Cluster
The cluster system is used when the Orchestra installation should be highly available. Therefore two Orchestra nodes can work together serving the same scenarios on different Orchestra nodes.
The nodes in this group use the same physical database. Furthermore they observe each other in order to detect dead group members. If a dead member is detected the current work is shipped to the remaining nodes that fulfill the open requests.The system consists of the following basic building block:
-
Administration over web browser ( on browser for all cluster nodes )
-
Two Orchestra servers that contain the Orchestra runtime components and is responsible for scheduling and executing the deployed interfaces
-
The Orchestra itself required a database that contains all persistent informations. Within the database configuration information (scenarios) and runtime state information is stored. The latter is required since it reflects the processing state of the scenarios and is necessary for restarting processes in case of a server crash.
-
The load-balancer is responsible for distributing processes over the different cluster nodes.
-
The cluster management is responsible for deployment of scenarios and also for implementing a heart beat that detects dead nodes and executes a cluster switch if necessary.
Further Information