Distributed operation is needed when one of the following applies:
• Available WAN bandwidth is poor or the WAN connectivity is suspect and suffers from high latency.
• The client does not deem the Customer Journey Management system to be a business critical service and prohibits competing for WAN bandwidth with other line of business applications at peak times.
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 established.
• Upon connectivity failure between remote Queue Agent and central Orchestra, local users continue to operate un-affected
• Distributed Queue Agent keeps local copy of runtime data.
• Distributed Queue Agent sends event data for statistical data handling to central stat server.
• Distributed Queue Agent provides connector interfaces and web terminals for local clients.