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.


Important

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.

Related topic

Understanding-distributed-operation-use-cases

See the topics listed in the following table to know how to map forms among three servers, with an example use case of servers located in San Francisco, Chicago, and Toronto. All the servers have DSO licenses. The topics assume that you are an administrator at Acme Industries. For more information, see Understanding-distributed-operation-use-cases. 

Action

Reference

Set up chained distributed transfers

Set up broadcast distributed transfers

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*