Distributed Operations
Distributed Operations is a unique Orchestra feature, which allows you to configure and manage your Customer Journey platform centrally, while the actual workload is distributed among all your Branches.
This also enables your Branches to attend to your Customers’ needs, even if the connection to the central server is lost. Poor network conditions, high latency and low bandwidth will thus no longer be a problem.
When do you need it?
Distributed Operation is needed when at least one of the following applies:
• Available WAN bandwidth is poor or the WAN connectivity is not 100% reliable and suffers from high latency.
• If there are several business critical systems, Orchestra being one of them, competing for WAN bandwidth, at peak times.
How does it work?
Distributed Operation is handled in the following way:
• Central Stat server handling persistence of all statistical data.
• Branches are configured to operate on remote Queue Agent instances.
• Distributed Queue Agent connects outbound to central Orchestra instance across WAN, communication is bi-directional, once connection is established.
• If the central server, or database, needs planned maintenance, or if there is an unexpected connectivity failure between remote Queue Agent and central Orchestra, local users continue to operate as usual, during the outage.
• The Distributed Queue Agent keeps a local copy of all runtime data and configuration.
• The Distributed Queue Agent sends event data for statistical data handling to the central Stat server, when a network connection is present.
• The Distributed Queue Agent provides connector interfaces and web terminals for local clients.
• Appointments for the current day are synchronized directly, so long as there is a network connection. Appointments for the next day, however, are synchronized nightly.
• Orchestra upgrades can be applied centrally, then applied to all Branches, using Remote Update. For more information, see
“Remote Update Overview” .
