...
FSM OP ECC MSGBROKER 1.0 - this is obsolete version of Message Broker and should not be used
FSM OP ECC MSGBROKER 2.0 - this is most commonly used version of Message Broker, requires .NET 4.7.2 ( check requirements for Message Broker 2.0 for Windows )
FSM OP ECC MSGBROKER 3.X - this is the latest version of Message Broker. Can run in:
Windows - check requirements for Message Broker 3.X for Windows
Linux - check requirements for Message Broker 3.X for Linux. This version in addition can be deployed in BTP
Several instances on a single server
FSM Message Broker is a lightweight component, which can be installed on an existing system beside already running software. However, some customers decide to set up a dedicated server for Message Broker. In such a case, it is usually expected, that development, test and productive instances of FSM Message Broker are installed in the same system, next to each other. Running several instances of Message Broker independently in the same server is fully possible, supported and as easy as running a single one. In order to achieve that, the FSM Message Broker archive needs to be extracted to the distinct directories (e.g. C:\Program Files (x86)\proaxia\dev, C:\Program Files (x86)\proaxia\test, C:\Program Files (x86)\proaxia\prod) and then configured accordingly paying special attention to avoiding conflict in file paths and port/URL binding, etc.
...