Page Comparison

...

Currently following FSM Message Brokers are available for download:

...

• Obsolete releases of Message Broker

  • 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

  • 0

• The recommended version of the 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

belongs to the 4.X serious. The latest release of Message Broker can be found and downloaded here.

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.

From now on, this document will assume a single version being installed however where it is considered important to notice the difference, it will be described in the document.

Table of contents