Performing the Deployment Process in SAP BTP, Cloud Foundry Runtime

The Cloud Foundry CLI is a popular tool among developers due to its simplicity, control, and direct feedback mechanisms.

The cf push command is your gateway to deploying apps. You have two main approaches:

• Push with defaults: Let SAP BTP, Cloud Foundry runtime handle configuration automatically.
• Push with custom settings: Specify configurations such as routes, environment variables, service bindings, and so on, either through command-line flags or a manifest.yml file.

Open your terminal, and log in to your SAP BTP, Cloud Foundry runtime, using the CF CLI: cf login -a API_ENDPOINT

Replace API_ENDPOINT with the API endpoint of your Cloud Foundry environment, which can be found in the SAP BTP cockpit of your subaccount.

Then, enter your credentials when prompted.

After logging in, configure the target organization and space: cf target -o YOUR_ORG -s YOUR_SPACE. Replace YOUR_ORG and YOUR_SPACE with the appropriate names.

Navigate to your application directory containing the manifest.yml file (if required custom settings), and run: cf push

Alternatively, you can deploy with custom settings using command-line flags when in the application directory. For example, run the following command to deploy an app named myapp with two instances, allocating 512 MB of memory each, and a custom route myapp-custom-host.mydomain.com: cf push myapp -i 2 -m 512M -n myapp-custom-host -d mydomain.com

After deployment, check the status of your application: cf app YOUR_APP_NAME Replace YOUR_APP_NAME with the name of your application. This provides details about the running instances, URL, memory usage, and more.

Ideal for rapid development, testing, and automation, especially for straightforward, single-component applications.

• Pushing your app with Cloud Foundry CLI (cf push)
• Deploying with app manifest
• App manifest attribute reference

The SAP BTP cockpit offers a user-friendly, graphical interface for managing and deploying applications.

Log in to your SAP BTP account, and navigate to the Cloud Foundry subaccount where you want to deploy your application.

• Navigate to the Applications page in SAP BTP cockpit.
• Select Deploy Application.
• A wizard labeled Deploy Application displays, prompting you to upload your source code.
• Choose the location of the file that contains your application. Select the location of the file containing your application. This can be a compiled binary like a JAR or WAR file or a source code archive.
• (Optional) manifest.yml file: If you want to use a manifest.yml file to specify application attributes, select the location of this file.
• (Optional) If you don't want to use a manifest.yml file, untick the Use Manifest box, and manually enter the application details, for example, application name, routes, and so on.

• Choose Deploy to initiate the deployment process. Then, the platform will handle the build and deployment of the application into the designated space.
• The SAP BTP cockpit will display the progress and status of your deployment in the list of applications. Once the application starts without a problem, the application’s status will turn green.

• Suitable for users who prefer a visual approach for application management.
• Optimal for quick deployments of uncomplicated applications.

• Deploy an application
• Tutorial: Deploy an application to SAP BTP, Cloud Foundry runtime

MTAs facilitate the deployment of complex applications involving multiple components across various technologies on the SAP BTP, Cloud Foundry runtime. You can choose from several methods based on your development environment and tool preferences.

Prerequisite: Access to an SAP BTP account with Cloud Foundry runtime enabled.

All these methods ultimately aim to package your MTA into a deployable format (.mtar file) and install it on the SAP BTP, Cloud Foundry runtime. They all require the descriptor file (mta.yaml), which specifies all necessary details about the application components, their dependencies, and the required services.

• Guided deployment with Business Application Studio (BAS) or SAP Web IDE Full-Stack: Automated deployment directly from the development environment. For more information, please check:

  • Developing MTAs in BAS
  • Developing MTAs in SAP Web IDE Full-Stack |

• Flexible deployment with Cloud MTA Build Tool (MBT): A command-line tool that builds and deploys based on your configuration, easily integrated into any IDE or CI/CD pipeline. Check out the following documentations for more support:

  Developing MTAs with MBT

• Custom deployment with manual configuration: Directly working with Cloud Foundry CLI and manually creating all necessary deployment artifacts to achieve maximum flexibility and granular control over the deployment process. Here are some documentations to walk you through this option:

  MTA Commands for the Cloud Foundry

Deciding on the right deployment methods depend on your specific circumstances:

• Large-scale enterprise applications with multiple integrated components.
• Microservices architectures needing seamless interaction.

• Multitarget Applications in the Cloud Foundry Environment
• Tutorial: Deploy in SAP BTP, Cloud Foundry runtime using MBT
• Tutorial: Deploy your first MTA using Multitarget CF CLI Plugin (manual configuration)

Container images encapsulate your entire application runtime environment, including the operating system, libraries, and dependencies. Deploying applications using Container images on the Cloud Foundry runtime within SAP BTP offers granular control over the runtime environment compared to buildpacks, enabling you to tailor configurations to meet your application's specific requirements. On the other hand, this approach requires you to assume full responsibility for managing the Docker image, such as applying security patches, updating dependencies, and so on.

Prerequisite: Access to an SAP BTP account with Cloud Foundry runtime enabled.

Use the cf push command with the --docker-image parameter to deploy your Docker-based application. For example:

cf push <APP-NAME> --docker-image <REPO>/<IMAGE>:<TAG>

Replace <APP-NAME> with your desired application name, <REPO>/<IMAGE>:<TAG> with the location and tag of your Docker image in the registry.

Applications requiring specific environments not supported by standard buildpacks.

Deploy Docker Images in the Cloud Foundry Environment

Continuous integration and delivery form a cornerstone methodology for automating software development and deployment processes, ensuring a systematic and error-minimized release pipeline.

• Continuous integration (CI): This practice involves developers frequently merging their code changes back to the main branch in a shared repository. Each merge triggers automated builds and tests, which helps to detect errors early and maintain code quality. It ensures that the main branch is always in a deployable state.
• Continuous delivery (CD): Extending CI, Continuous Delivery automates the release process so that the software can be deployed at any time with by choosing a button. It typically involves an automated testing phase that validates if the changes can be released into production, followed by an automated or manual release process.

SAP provides two primary solutions for implementing CI/CD on the SAP BTP, Cloud Foundry runtime:

• SAP Continuous Integration and Delivery (CI/CD): A managed service that facilitates straightforward setup and execution of predefined CI/CD pipelines, ideal for standard deployment processes. Refer to the Help Portal of SAP Continuous Integration and Delivery for more information.
• Project "Piper": An open-source initiative offering customizable Jenkins pipelines and Docker images, suitable for complex workflows requiring specific configuration adjustments. Check out the official documentation of Project Piper for more support.

Prerequisite: Access to an SAP BTP account with Cloud Foundry runtime enabled.

• Step 1: Code integration Developers push changes to a version-controlled system like Git, which are then automatically integrated into the main line through a CI server.

• Step 2: Automated testing Each integration triggers an automated test suite encompassing unit, integration, and, sometimes, acceptance tests to ensure functionality and performance.

• Step 3: Preproduction staging Successful builds are deployed to a staging environment that mirrors production to test real-world behavior and performance under load.

• Step 4: Production deployment Upon successful staging tests and final approval, changes are deployed to production. This step can be automated or require manual intervention, depending on the organization’s deployment policies.

• Effective for large-scale enterprise applications requiring robust architectures with frequent updates and multiple developers.
• Useful in regulated environments where traceability and audit trails of changes are required.

• Tutorial: Set up a CI/CD pipeline for SAP BTP, Cloud Foundry runtime
• Tutorial: Configure and run a predefined SAP Continuous Integration and Delivery (CI/CD) pipeline

This lesson provided a comprehensive exploration of application deployment within SAP BTP Cloud Foundry runtime, highlighting the versatility of CF CLI and SAP BTP cockpit. It delved into advanced deployment strategies including multitarget applications, Continuous Integration/Continuous Delivery pipelines, and Docker images, which facilitate the management and deployment of complex applications. By mastering these tools and techniques, you can optimize the deployment processes, ensuring you can keep pace with growing operational demands.