4.X - Prerequisites for deployment

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 1. SAP Cloud Connector
2 2. Create and configure Cloud Foundry services
- 2.1 2.1. Authorization & Trust Management
- 2.2 2.2. Destination
- 2.3 2.3. Connectivity
3 3. Acquire Message Broker for Linux
4 4. Configure the manifest file
- 4.1 4.1. Cloud Foundry configuration
- 4.2 4.2. Message Broker configuration
  - 4.2.1 4.2.1. NLog configuration
  - 4.2.2 4.2.2. Message Broker configuration

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.

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.

Service Marketplace in SAP BTP cockpit. Services whose instances should be created before Message Broker deployment are highlighted.

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

Service management in the SAP BTP Cockpit

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.

2.2. Destination

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

Destination Configuration in service ‘proaxiacf_destination’

The following Destination Configuration properties should be customized:

Property name	Comment

Property name	Comment
Destination name
Type	E.g. ‘HTTP’
Proxy type	Possible values: · 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.
Authentication way
User
Password
Address URL	Consists of Cloud Connector virtual host (e.g. saperd:443) concatenated with partial webservice URL (e.g. /sap/bc/srt/rfc for all web services).

URL in the Destination Configuration

Virtual Host in Cloud Connector Administration

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

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.
SapDefinitions	BtpDestinationPath	Path to the SAP web service (not including the part entered in the Address URL field of the destination cloud service).

Learn more about the configuration properties: [LINUX 3.X] Application config filearchived