...

Cluster Architecture

Redundancy and restart capability is provided by clustering the JS7 products for automated fail-over as follows:

• The JOC Cockpit can be operated for an active-passive cluster with one active instance and any number of passive instances.
  • Fail-over is handled automatically within 60s between cluster members by the JS7 - Cluster Service.
  • The JOC Cockpit cluster relies on a persistence layer provided by the JS7 - Database.
• The Controller implements an active-passive cluster with one active instance and one passive instance.
  • The Controller implements clustering and journaling by itself and does not require additional products such as a DBMS, see JS7 - Controller Cluster.
  • Cluster members couple and synchronize automatically. Fail-over time is typically around 3s.
• The Agent offers both an active-passive cluster and an active-active cluster, see the JS7 - Agent Cluster article.
  
  

Image Added

Communication

Asynchronous communication is based on the fact that messages are sent to a partner product without relying on the availability of the given productt: it is neither guaranteed that a message is received by its recipient nor can be assumed that the recipient will be able to respond in good time.

...

• The Controller and Agents raise events for order state transitions.
• The Controller subscribes to events that originate from Agents. The JOC Cockpit subscribes to events that are forwarded from a Controller.
• The asynchronous nature of events is handled by the receiving product. Any events remain in place with the originating product until the receiving product confirms receipt. Only then events are released from the originating product.

Further

...

Resources

• JS7 - System Architecture
• JS7 - JOC Cockpit Cluster
• JS7 - Controller Cluster
• JS7 - Agent Cluster