Chained and broadcast distributed transfers

The information in this topic is applicable only for on-premises deployments.

Chained and broadcast distributed transfers involve multiple servers, for example:

• A chained distributed transfer occurs when the sanfrancisco server transfers a request to the chicago server, and then the chicago server transfers the request to the toronto server.
• A broadcast distributed transfer occurs when the sanfrancisco server transfers the same request to two servers, chicago and toronto.

Consider the overhead that might be involved in the implementation and maintenance of these features. When data is distributed among more than two sites, your troubleshooting effort might increase exponentially.

The examples in the following sections explain how to map forms among three servers located in San Francisco, Chicago, and Toronto. All the servers have  licenses. The topics assume that you are an administrator at Acme Industries (see Distributed-operation-use-cases).