The information in this topic is applicable only for on-premises deployments.
Each distributed mapping lets you define two locations. To transfer requests among more than two locations, you can chain mappings together. Mapping chains enable you to reduce the total number of mappings in your system. For example, suppose you have the following mappings:
Mapping A transfers requests from toronto to sanfrancisco
Mapping B transfers requests from sanfrancisco to chicago
Mapping C transfers requests from chicago to toronto
To transfer requests from toronto to chicago, you can either create another mapping from toronto to chicago or reuse existing mappings by chaining Mapping A to Mapping B.
Tip
Create a separate mapping chain each time you have a different starting and stopping place. Doing so avoids the looping issue that might occur if you create one mapping chain from sanfrancisco to chicago, chicago to toronto, and toronto to sanfrancisco to transfer copies with ownership.