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.

 

Table of Contents

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.   

...

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:

...

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

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.

...

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:

...