Message Broker

FSM Connector Message Broker is an application that sits between SAP ECC or S/4 backend and FSM Cloud and participates in data exchange between these systems. The data are sent as asynchronous messages. Message Broker supports in sending the messages to and fetching the messages from the Cloud, with support for FSM messaging protocol to ensure

• the messages are always delivered to the target system, no messages are lost

• the messages are delivered to the target system in a sequence, in which they were generated on the source system

The delivery guarantee is based on several types of confirmations, which allow the source system to mark the messages as received on the target. To deliver the messages in the right sequence, while not scarifying performance, the messages are put in queues, bundled together, etc. As the Message Broker queues are held in memory, restart of the service could cause message loss. To resolve this problem, Message Broker on its start-up sends so-called resend request to SAP backend. The backend sends again all messages that have not been confirmed by the Cloud. There is a similar mechanism for the reverse channel – the Cloud resends the messages to ECC/S4HANA until they have been confirmed.

To achieve the goals described above, Message Broker must run as a stateful single-instance application. In other words, for each FSM account + company combination, there must be only one Message Broker running at the given point in time. If there were several active instances running and handling a message for the same account and company, the right sequence of message processing could not be guaranteed. E.g., instance A could be faster in processing messages than instance B, causing messages processed by A to arrive to the target system before messages of instance B, even if they were sent later.

Message Broker component overview

Open

Message Broker communication overview

Open

Open

Open

Message Broker installation files

1. Message Broker is delivered as binary files (ZIP file) separately for Windows and Linux

• Linux version can be used in BTP

• x86 is only supported architecture

2. Message Broker can be downloaded from SAP download center (links are also published on the dedicated Connector’s documentation site)

3. Message Broker versioning - there are two parallel ways of MB versioning:

   • One relies on the version of the Message Broker DLL

   • The other one relies on the component version in SAP download centre

   • As these are not related to each other, Proaxia documentation delivers versions’ matrix

Learn more about Message Broker installation and setup: How to install the Message Broker - reliable guide