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.
...
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.
...
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 - see https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1350205443/Prerequisites+for+deployment#2.2.-Destination).). E.g. |
| 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 |