Introducing SAP BTP Services for DevOps

Objectives

After completing this lesson, you will be able to:

  • List which DevOps services are part of the recommended DevOps setup on SAP BTP

SAP BTP Services for DevOps

Note
This lesson is geared mainly towards administrators, but any of the roles involved could benefit from it.

While you already discovered certain SAP BTP services and offerings, in this lesson you can start exploring the recommended setup for applying DevOps principles on SAP BTP.

You will find out about all SAP BTP DevOps services, with a short description and potential alternatives (in case you want to break out of the recommended setup for certain aspects along the life-cycle).

Recommended Setup for DevOps on SAP BTP

If you want to implement the recommended approach from SAP for DevOps with SAP BTP, use the following animation to discover more information on the involved SAP BTP cloud services. You will see three SAP BTP sub-accounts, which serve the following purposes:

  • Development, for development of your app
  • Pre-Production, for testing your app in a representative environment.
  • Production, for releasing the version of your app that will be adopted by end users.

First click on the play button below to see the landscape, then click on the "+" buttons to find more details.

Steps for Continuous Integration (CI)

1. Setup CI

DevOps with SAP BTP includes SAP Continuous Integration and Delivery service, a 'Pipeline-as-a-Service' offering for CI/CD, with templates for SAP-specific use cases. You can consider these templates like golden paths that reflect SAP best practices for the given development use cases. This offering allows you to come up with a running CI/CD pipeline for an SAP-specific use case in minutes.

2. Develop

The pipeline is then used by the development team to qualify their changes, such as being made in SAP Business Application Studio (or other development environments). The changes get pushed into a Git-based source code repository, which triggers the execution of the associated pipeline via webhooks. The automated tests that are comprised in this pipeline then get executed and their outcome provide feedback to the developer on the quality of the change - is development done or are further changes required, as the tests did not succeed.

3. Deliver

The pipelines also allow an optional automated hand-over of qualified release candidates into transport management. This enables you to apply a standardized, enterprise-ready change management process, with additional control towards your production environment. For example, you can define who can come up and handle changes in which sub-account, which enables you to enforce company policies.

The recommended option for transport management is SAP Cloud Transport Management service, as it covers more and more application-specific content types besides development content. For example, think of portal sites from SAP Launchpad service or integration flows of SAP Integration Suite.

Alternative to SAP Cloud Transport Management is the usage of the enhanced Change and Transport System (CTS+). This is part of ABAP on-premise servers and can cover only content in the format of Multi-target Application (MTA) archives. There are no plans to extend the content coverage of CTS+ beyond this development content.

For additional control, you can integrate transport into change management processes - running on SAP Cloud ALM or existing processes powered by SAP Focused Run/SAP Solution Manager. These allow you to synchronize the propagation of cloud changes with on-premise changes, for hybrid scenarios.

4. Operate

To enable a reactive way of working, you use SAP Alert Notification service for SAP BTP to subscribe to relevant events around your app - be it from used SAP BTP services, from the infrastructure providers or with custom alerts from your application. Also, you can get notified about outcomes of pipeline runs and performed transports. You can then consume these alerts via your channel of choice.

These alerts can then automatically trigger recommended actions - such as for alert remediation, executed by SAP Automation Pilot service.

Also, you can use this cloud service to reduce manual efforts for recurring technical operations tasks along the life-cycle, such as daily operations tasks.

SAP BTP operations services can smoothly be integrated - for example, alerts from SAP BTP can easily get routed by SAP Alert Notification service for SAP BTP into health monitoring capabilities of SAP Cloud ALM that then trigger and orchestrate automated operation flows executed on SAP BTP, by SAP Automation Pilot service. For third-party operation platforms, open APIs are offered for integration.

Note
Although being highly integrated, you can also decide to use only single DevOps cloud services, as they are not dependent on each other.

Summary

You now have gained insights on the recommended setup for applying DevOps principles around your development projects on SAP BTP - including an overview of all involved SAP BTP services, their interplay, and potential alternatives.

Further Reading

To use the services above, you have to subscribe to them via SAP BTP Cockpit and perform an initial setup of each of the services, as described in SAP Help Portal.

For more information, also see this hands-on video series from SAP HANA Academy: DevOps with SAP Business Technology Platform | Hands-on Video Tutorials | SAP Blogs

Log in to track your progress & complete quizzes