This documentation applies to the 8.0 version of Remedy Action Request System, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Chained and broadcast distributed transfers

This section contains information about:

Both 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 this section assume that you are an administrator at Acme Industries (see Distributed operations scenarios). You are mapping forms among three servers located in San Francisco, Chicago, and Toronto. All the servers have DSO licenses.

The procedures in this section build on procedures in Distributed operations scenarios.

Was this page helpful? Yes No Submitting... Thank you

Comments