1.Go to the Monitor Replicator page under the Packages tab for the target, found on the Application Management page. You can see that a conflict occurred where the status is "warning" on the inbound package.
2.Select the map name to open package details, where you will see that there was a conflict.
3.The default conflict setting is set to automatically Skip. This means that the newer change is automatically applied on the source, and the older package from the source is skipped with a status of "rejected", rather applying the newer version from the target on both. The result should be that when you refresh your source web application, you will see a "2" at the end of the title.
In this scenario you:
·Modified an event on both the source and target, with different prefixes for the titles.
·Monitored the process of conflict handling.
·Viewed the package details for the package on the target source, using the Replication Package Details page.
The expected result is that Replicator handles conflicts as specified, and that the Replicator conflict management functions as specified in configuration. In this case that the conflict automatically Skips by applying the newer change on the source.
For further detailed instructions and information about conflict handling see the "Monitor Conflicts" section in the Replicator Reference Guide.
Also see the following Scenario User Guide article for further conflict handling details: Conflicts in Replicator: Best Practices and Configuration.
This scenario demonstrates the capability of Replicator to replicate in-process workflows. You must first ensure that capturing workflows is selected on your Map Family configuration settings. You will then add a workflow, start it on an item, and complete the workflow.
1.Go the Manage Map Families in Central Administration for both your source and target web applications. Select the Map family, and click View Maps.
2.Select the Map Family, this will take you to the Configure Replication Map Settings page. Here, select All Events for workflows.
4.In a web browser, open your source web application.
5.Add an Approval workflow to a list or library.
6.Start the approval workflow on an item in the list or library.
7.Complete the workflow by approving the workflow task item.
1.Check the progress of replication on the Monitor Replicator page under the Packages tab and wait for the replication of the above actions to complete.
2.In a web browser, open your target web application.
3.Check that the Approval workflow created above is available on both the source and target list or library.
4.Check to see that the approval workflow has run on the item on the target and the workflow status for the item is "Approved".
In this Scenario you:
?Checked to see that the workflow task on the target was replicated and completed.
?Checked that the workflow was successfully added, and the addition was replicated from source web application to target web application.
?Checked that the workflow was successfully started, and replicated from source web application to target web application.
?Checked that the workflow was successfully completed by approving; approval was replicated from source web application to target web application.
The expected result is that Replicator is able to replicate the starting of the approval workflow and is able to replicate the approval of the item.
This scenario demonstrates how to set up a multi-hop scenario where replication will occur between three different web applications. The web applications will be called Corporate, London, and Hong Kong.
1.Set up your environment as detailed in the Metalogix Replicator Installation Guide. Be sure you set up bidirectional replication between two web applications. For this scenario we'll call these two web applications London and Corporate.
2.Enable a web application; we will call this web application Hong Kong in this scenario. In order to enable the web application for replication, go to the Configure Application page found in the Metalogix Replicator section of the SharePoint Application Management page.
3.Go to the Manage Replication Groups page, found in Application Management for your Hong Kong web application.
4.Select Add Group and title your group "Branch Offices Group" so that it matches the group that London and Corporate are a part of. Click Ok.
5.Set up a connection connecting Hong Kong to London. Do this by selecting Manage Replication Connections in Application Management.
6.Select Add Connection and title your group descriptively Hong Kong to London. Complete the Target Web Application section using London's information and credentials. Disregard the Target Replication Passphrase for this section.
7.Test the connection.
8.Add Branch Offices Group to the selected replication groups and Click Ok.
9.On your London web application go to the Manage Replication Connection page, found in Application Management. Create a connection from London to Hong Kong. The Target Web Application section should use Hong Kong's information and credentials.
10.Test the connection.
11.Add Branch Offices Group to the selected replication groups and Click Ok.
12.Verify that the "Portal Map Family" has replicated over to Hong Kong automatically by checking in Manage Map Families, found in Application Management.