Cell System
The cell communication is a basic mechanism that is used for distributed communication between Orchestra instances. Hereby scenarios can access services and send signals to distributed Orchestra instances. The concept of the cell communication is designed to be locations transparent. Therefore a developer must not care about the physical distribution. When a service is invoked or a signal is sent, Orchestra infers all responsible nodes in the cell network. It redirects the call or signal to the responsible instance. For a developer it is not relevant if the service that incorporate with each other are running in the same instance or are distributed by a cell-network.
-
Administration over web browser
-
Orchestra server that contains Orchestra runtime components and is responsible for scheduling and executing the deployed interfaces
-
The Orchestra itself required a database that contains all persistent information. 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 crashes.
-
Between the cell nodes a cell communication is established. This communication ensures that service calls or signals can be distributed smoothly without any knowledge.
Usage scenarios for cell communication:
-
Connect an internal Orchestra with the internet over an demilitarized zone
-
Different Orchestra instances on distributed company locations
-
Manual load distribution
The distribution mechanism is available for following scenario elements:
-
Partner-Management (partner-send, partner-publish)
-
Signals
-
Orchestra services