Message Broker is delivered as a zip archive, which contains executable files and a configuration template. Downloadable archives can be found here: https://launchpad.support.sap.com/#/softwarecenter/search/ECC%20MSGBROKER. The relevant archive needs to be downloaded first and then extracted to a target directory on the server (i.e. C:\Program Files (x86)\proaxia in windows server). The exception here is FSM Message Broker running in BTP - in this case file must be deployed in a cloud account.
Currently following FSM Message Brokers are available for download:
Obsolete release of Message Broker
FSM OP ECC MSGBROKER 1.0
FSM OP ECC MSGBROKER 2.0
FSM OP ECC MSGBROKER 3.0
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