Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Before performing the deployment of Message Broker, it is necessary to setup SAP Cloud Connector, create and configure three cloud services, acquire the Message Broker for Linux and configure its manifest file.

...

Cloud Foundry services are managed in the Services/Instances->Instances tab.

...

Service management in the SAP BTP Cockpit

 

It is recommended to use the following naming convention for service instances:

...

The Authorization & Trust Management service provides authentication keys necessary to execute the Destination service. Create it with a name following the naming convention. The service must be assigned to the ‘application’ plan.   

...

2.2. Destination

The Destination service is used to configure the endpoint connection with the backend system.

...

  • Destination name

  • Type - e.g. HTTP

  • Proxy type:

    • Internet – Direct connection to ECC system, without SAP Cloud Connector. Requires ECC web service to be exposed to the internet.

    • On Premise – Connection via SAP Cloud Connector and its VPN tunnel, recommended

  • Authentication way - e.g. BasicAuthentication

  • User / password - technical user in SAP (see also FSM technical user authorization in ERP)

  • Address URL - Consists of Cloud Connector virtual host (e.g. sapabc:443) optionally concatenated with partial webservice URL (e.g. /sap/bc/srt/rfc). 

Example Address URLs: http://sapabc:443 (without webservice URL), http://sapabc:443/sap/bc/srt/rfc (with URL for all web services).

  • Proxy type:

    • Internet – Direct connection to ECC system, without SAP Cloud Connector. Requires ECC web service to be exposed to the internet.

    • On Premise – Connection via SAP Cloud Connector and its VPN tunnel, recommended

  • Authentication way - e.g. BasicAuthentication

  • User / password - technical user in SAP (see also FSM technical user authorization in ERP)

  

2.3. Connectivity

The Connectivity service is necessary for Cloud Connector connectivity.

...

The manifest.yaml file contains configuration related to the Cloud Foundry, as well as configuration specific for Message Broker. It can be edited on the local computer, in any text editor.

...

Cloud Foundry-related configuration in the manifest file

 

4.1. Cloud Foundry configuration

...

Cloud Foundry uses console for logging.

...

Log-related configuration in the manifest file

 

4.2.2. Message Broker configuration

...

Message Broker-related configuration in the manifest file

 

The following properties are specific for BTP deployment:

SapDefinitions

BtpDestination

Name of the destination configured in the destination cloud service.

BtpDestinationPath

Path to the SAP web service (not including the part entered in the Address URL field of the destination cloud service). E.g. /sap/bc/srt/rfc/pacg/ecm_ws/900/pacg_ecm_ws/

 

Info

Learn more about the configuration properties: 3.X - Message Broker application config file. See an example configuration file: Example Message Broker configuration for BTP