Page History
...
- The Controller Cluster brings high-availability including fail-over capabilities for the deployment of scheduling objects and for execution of workflows.
- Two Controller instances are operated on different servers to synchronize JS7 - Order State Transitions and log events.
- Automated fail-over guarantees high-availability and restart capabilities capability of a Controller Cluster (passive cluster).
- Use of the Controller Cluster is subject to the agreements of the JS7 - License.
...
- Network connections are established from both Controller instances to the Cluster Watch Agent.
- This scenario does not offer high availability for the Agent acting as a Cluster Watch.
- The Cluster Watch Agent is required to be available at the point in time when a Controller Cluster fail-over should occur.
Display feature availability EndingWithRelease 2.6.0
Integration with JOC Cockpit
A single JOC Cockpit instance or any number of clustered a JOC Cockpit instances Cluster can be used to connect to a Controller:
- JOC Cockpit makes use of the built-in Proxy Service to connect to the Controller. This includes automatically switching the active Controller instance in the case of fail-over or switch-over of a Controller.
- JOC Cockpit receives state information from a Controller that is added to the history, e.g. for example log events, and that is visualized in the GUI (order state events).
...
Overview
Content Tools