Deployment process

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.

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):

1.2. Login into Cloud Foundry

Execute the following command:

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

Select one of the spaces.

Open

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:

Open

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

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].

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