Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Although it is recommended to use the latest version of product versions of FSM Connector and Message Broker are not entirely dependant. This means that it is possible to use the newest FSM Connector with one of the older message brokers and vice versa but certain functionalities may not work then like for instance failover mechanism which needs both: the newest FSM Connector and FSM Message Broker

3070721 - Download of FSM Message Broker

  • Message Broker 3.4 - released on 30.05.2022

  • Handling for failover mechanism was added

  • New message broker makes is possible to remap existing FSM Cloud GUIDs to new SAP keys keeping existing FSM relations in place

  • Message broker is now capable of presenting it’s own version

  • Message Broker 3.3 - released on 21.01.2022

  • In case of configuration errors in MessageBrokerSettings.yaml, Message Broker used to exit without any information, now a meaningful log is produced before the application is stopped

  • Message Broker 3.2 - released on 28.12.2021

  • Message Broker 3.1 - released on 23.08.2021

  • Message Broker 3.0 - released on 28.06.2021

  • Message Broker 3.2 was built against .NET 6.0

  • Improved handling of container restart in BTP (required also changes in SAP backend. Check SAP NOTE 3133310

  • Pinging Message Broker from Connector does not result in ERROR entries in the log. INFO is added instead

  • In case a proxy is used relevant information can be found in the log

If you want to learn about about Message Broker go to FSM Message Broker installation & configuration

  • No labels

If you'd like to help us improve the documentation, please provide your feedback using the communication channels listed here. Learn about support possibilities here.