Page Comparison

...

Panel
panelIconId 2757 panelIcon :exclamation: panelIconText ❗ bgColor #FFC400
Currently, only two message brokers can run in parallel where one of them is active and the other one inactive

In order to meet the requirements described above and, at the same time, cover the requirements towards failover capable solution Message Broker (>=

Status
colour Blue title message broker 3.4

) can be started in inactive mode. Inactive instance is in a standby, not participating in message exchange, and waiting for an activation signal. This influences both direction directions of messaging:
• Outbound messages, sent from ECC to FSM Cloud must only be sent through an active Message Broker instance.
• Inbound messages, sent from FSM Cloud to ECC are retrieved with a polling. The Cloud never actively pushes any messages to Message Broker. Instead, Message Broker polls the cloud to check if there are any new data to be processed. On the inactive Message Broker, the polling must be disabled. Only the active instance can poll the Cloud.

For the outbound case, there must be a dispatcher that takes care for watching, which Message Broker is active and sending the messages to this instance. To avoid another single point of failure and simplify the architecture outbound message dispatching was built into FSM Connector (

Status
title (S4)pacg 200 sp05

). This is done via heartbeat mechanism. Heartbeat calls allows the FSM Connector to keep track of available Message Brokers.

...