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.
1. SAP Cloud Connector
As presented on the diagram in chapter 1.2. Architecture overview, the recommended integration architecture uses SAP Cloud Connector (not to be confused with FSM Cloud Connector which provides business logic handling) as a link between Message Broker (as an SAP BTP application) and SAP ECC/S4 HANA.
It is strongly recommended to use the latest version of SAP Cloud Connector. It will help to avoid unnecessary issues.
2. Create and configure Cloud Foundry services
It is required to create instances of the following cloud services:
· Destination
· Authorization & Trust Management
· Connectivity
Additionally, Cloud Foundry Runtime Service needs to be licensed to deploy the application. You can use the SAP Estimator Tool to estimate price of the BTP solution: https://www.sap.com/products/business-technology-platform/estimator-tool.html?blueprintId=bb7c129b-d0c9-4220-b299-e6010f040b74
Service instances can be created using the Service Marketplace tab in SAP BTP Cockpit.
Cloud Foundry services are managed in the Services->Instances tab. It is recommended to use the following naming convention for service instances:
‘proaxia_ + service type’ (e.g. ‘proaxiacf_destination’).
2.1. Authorization & Trust Management
The Authorization & Trust Management service provides authentication keys necessary to execute the Destination service. Create it with a name following the naming convention.
2.2. Destination
The Destination service is used to configure the endpoint connection with the backend system.
%20free%20Destinations%20-%20SAP%20BTP%20Cockpit%20-%20Googl.png?version=2&modificationDate=1704721724364&cacheVersion=1&api=v2&width=1252&height=416)
The following Destination Configuration properties should be customized:
Destination name
Type - e.g. HTTP
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.
3. Acquire Message Broker for Linux
Since Cloud Foundry containers are Linux-based, it is necessary to acquire the Linux version of Message Broker. Such a version consists of the main Message Broker file (unix executable file) and manifest.yaml.
4. Configure the manifest file
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
The following properties are related directly to the Cloud Foundry:
Property | Description |
|---|---|
Name | Set the Cloud Foundry application’s name (to be displayed in the SAP BTP Cockpit). |
Memory | Memory allocation, e.g. 256M. |
Disk_quota | Storage allocation, e.g. 128M for CLI deployment, deployment using the built-in tool requires more storage, e.g. 512M. |
Buildpacks | Use the binary_buildpack for binary compilation/dependencies setup. Do not change the build pack. |
Command | Set execution authorizations for the file and execute the Message Broker (as a binary file). |
Services | Message Broker uses three standard cloud services: proaxiacf_aaplauth, proaxiacf_destination and proaxiacf_connectivity. These services should be created in Cloud Foundry before Message Broker deployment. |
4.2. Message Broker configuration
Configuration specific for Message Broker is maintained within the Env section.
4.2.1. NLog 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). |
Learn more about the configuration properties: 3.X - Message Broker application config file. See an example configuration file: Example Message Broker configuration for BTP