/
Outgoing Service (SAP to FSM) - BTP Case

Outgoing Service (SAP to FSM) - BTP Case

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 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.

 

Related content

Incoming Service (FSM to SAP)
Incoming Service (FSM to SAP)
More like this
Prerequisites for deployment
Prerequisites for deployment
Read with this
Outgoing Service (SAP to FSM)
Outgoing Service (SAP to FSM)
More like this
Deployment of Message Broker to SAP BTP
Deployment of Message Broker to SAP BTP
Read with this
Enable use of HTTPS in the Message Broker's config
Enable use of HTTPS in the Message Broker's config
More like this
Setting up secure (HTTPS) connection from SAP system to FSM Message Broker.
Setting up secure (HTTPS) connection from SAP system to FSM Message Broker.
Read with this

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