Handling Delivery with Transports

Objectives

After completing this lesson, you will be able to:

Describe how changes are handled using transport management
Use SAP Cloud Transport Management service at a basic level

Handling of Changes Using Transport Management

In a previous lesson, you modeled your delivery landscape in SAP Cloud Transport Management.

In this lesson, you will learn how to use SAP Cloud Transport Management to deliver content to your target environments. For this, you will discover a typical example of SAP Continuous Integration and Delivery service uploading a multi-target application (MTA) archive to SAP Cloud Transport Management. You will manually trigger the import of the resulting transport request.

You will check the import logs and find options to schedule an automatic import.

Transport Concept

The following figure shows an example of a transport landscape. We use the SAP Continuous Integration & Delivery service to create a transport request and export an application to the SAP Cloud Transport Management service.

Example of a transport landscape

The Usage of SAP Cloud Transport Management Service at a Basic Level

In our example, the first target for deployment will be the development subaccount. This deployment is (optionally) performed in the release stage of the SAP Continuous Integration and Delivery service. As a second step the SAP Continuous Integration and Delivery service ‘exports’ the application from the development node, Therefore, the transport request is initially placed into the import queue of the Test transport node.

You can trigger the import into the Test sub-account from SAP Cloud Transport Management from the queue. After the deployment, you can perform additional tests on the Test sub-account, such as central integration tests.

At the same time, the transport request will be forwarded into the import queue of the successor node in our transport landscape, in our example the production transport node.. If everything is fine, you handle the import into the final target node.

All changes will be reflected in a central log file, which you can use for auditing.

To get a first feeling about how a transport is handled in the SAP Cloud Transport Management Service, watch the following demo video. This will allow you to manage the propagation of changes along a predefined delivery landscape by a clearly defined set of delivery managers, respecting existing rules and boundary conditions about handling changes in your production environment.

Note

Please note that the requests shown in the video are not necessarily all transport requests. By default, the list shows transports of the last 7 days that would be importable due to their status or where the import is currently running. More older transport requests could also be ready for import. Change the preset date range if you want to see them.

If you click on import all, this must be considered. This triggers the import of all transport requests in an importable status (initial, repeatable, fatal), even if they should not be visible on the list with the current filters. You receive a corresponding warning if you click on Import All.

Summary

You are now able to:

Trigger imports in SAP Cloud Transport Management.
Check the result and log of an import.

Further Reading

SAP Cloud Transport Management documentation

Documentation on starting an import

Documentation on scheduling imports

Tutorial video series on SAP BTP DevOps including SAP CI&D service, cTMS and SAP Alert Notification service

Log in to track your progress & complete quizzes