View Source

In case you have your message broker installed in BTP there are view exceptions with respect to what is described in Outgoing Service (SAP to FSM).

In the case of Message Broker running in BTP you cannot decide which protocol should be used - HTTPS is enforced same as the port number which is always 443.
The correct URL of the Message Broker service can be found in BTP in the ‘Application Routes’ section:
The address misses only the PATH component and referring to https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/6293971/Outgoing+Service+SAP+to+FSM#HTTPSettings the URL Access Path properties should be following:
- Protocol: HTTPS
- Host: FSM_Message_Broker.cfapps.eu10.hana.ondemand.com
- Port: 443
- Path: this does not change and path comes from message broke configuration file like in non-BTP case

Port 443 is predefined for HTTPS connections and considered a standard, that’s why it doesn’t even have to be explicitly entered when the web address starts with HTTPS

EXAMPLE

Using the address https://FSM_Message_Broker.cfapps.eu10.hana.ondemand.com taken from picture above and path /fsm/SendOutboundMessageService.

FSM Cloud Connector > Outgoing Service (SAP to FSM) - BTP Case > proaxia_recording-4.gif