Page Comparison

The deployment process can be performed using the Cloud Foundry CLI. Another approach - deployment via BTP cockpit - used to be available, but at the moment cannot be used. This method also consumed more disk quota.

Table of Contents

minLevel	1
maxLevel	7

1. Deployment with the Cloud Foundry CLI (recommended way)

1.1. Download and install the Cloud Foundry CLI

To download and install the Cloud Foundry Command-Line Interface, follow the steps described on the official Cloud Foundry documentation site:

https://docs.cloudfoundry.org/cf-cli/install-go-cli.html

Verify proper installation by executing the following command in your command line tools (e.g. in Command Prompt on a Windows system):

Code Block
cf --help

1.2. Login into Cloud Foundry

Execute the following command:

Code Block
cf login

Enter the API endpoint, an S-User email address and its password.

Info
Cloud Foundry CLI works always with SAP Identity Provider, therefore S-User email/password should be used here, even if the Cloud Foundry account was configured to use a custom Identity Provider.

Select one of the spaces.

Command 'cf login' in the command line tool

1.3. Run the deployment process

Navigate to the catalogue where the Message Broker files are stored (e.g. using command cd [path]). Make sure that the manifest file is on one level with other Message Broker files, as below:

Image Added

After switching to the Message Broker’s directory, start the deployment process with the following command:

Code Block
cf push

The course of the application creation process is communicated on the screen, as shown below:

Command 'cf push' in the command line tool

1.4. Find the application in SAP BTP Cockpit

The deployed application should be visible in the Applications tab of the SAP BTP Cockpit. Its state should be Started.

Message Broker as a running application in the SAP BTP Cockpit

Logs generated during Message Broker start can be found in SAP BTP Cockpit, in the Logs tab:

Application logs generated during Message Broker start

You can also trace them in the Cloud Foundry application (e.g. in Windows Powershell) by using command cf logs [appname].

Info
As URL access path for outbound webservice (Outgoing Service (SAP to FSM)) use the Application Route for the Message Broker application (to be found in app overview) concatenated with web service URL path from the manifest file. E.g. https://FSM_Message_Broker.cfapps.eu199.hana.ondemand.com/e4c/SendOutboundMessageService

2. Deployment with the built-in ‘Deploy application’ feature

Note
It’s been reported that deployment via ‘deployment application’ does not work. If this is still the case we could only advice using the first method and opening OSS ticket.

Expand

title	Deployment with the built-in ‘Deploy application’ feature

Keep in mind that using this deployment approach involves download of numerous build packs, therefore requires allocation of more disk space in the manifest file (e.g. 512M):

The Cloud Foundry-related configuration of the manifest file, property ‘disk_quota’

2.1. Use the Deploy application button

Navigate to the Applications tab in SAP BTP Cockpit and click the Deploy Application button.

The ‘Display Application’ button in the SAP BTP Cockpit

Specify the Message Broker’s and its manifest’s location. The Message Broker files (File location) should be compressed into a zip file, while the manifest file (Manifest location) should be a separate .yaml file.

File paths necessary for application deployment

Click Deploy.

2.2. Find the application in SAP BTP Cockpit