Reflecting Your Delivery Landscape in Transport Management

To reflect your delivery landscape in SAP Cloud Transport Management, you have to perform two significant steps:

1. Set up SAP Cloud Transport Management. This must normally be done only once, on a dedicated subaccount for centrally shared administrative services, because all your delivery landscapes can be managed from one central instance of SAP Cloud Transport Management. Only if you want to restrict visibility for easier handling of large landscapes (so that a delivery manager only sees the relevant nodes that she is authorized to handle) or if you need more file quota for transports, you can optionally set up several instances of SAP Cloud Transport Management. For this, SAP Cloud ALM does allow connecting to several instances of SAP Cloud Transport Management.
2. Configure your delivery landscape inside your SAP Cloud Transport Management instance. This step must be completed for every transport scenario you wish to implement.

For more information on this topic, see Setting Up Your Account Model | SAP Help Portal in the SAP BTP Administrator’s Guide and view the video, Reflecting Your Delivery Landscape in Transport Management.

As a release manager of Rotating Banana, you have used a typical three-sub-account landscape in SAP BTP for your extension projects. The sub-accounts for development, testing, and production have already been set up.

As an SAP BTP administrator at Rotating Banana, you have decided to run SAP Cloud Transport Management in a separate administrative sub-account to allow for strict access control. If the developers would like to get read access to SAP Cloud Transport Management to check the results of the transports this can be achieved by assigning them the Cloud Transport Management Viewer role.

Therefore, you entitle the administrative sub-account for SAP Cloud Transport Management and subscribe to it. You create three role collections (SAP Cloud Transport Management Administrator with full access, Transport Manager with all transport-related authorizations and a Viewer with display authorizations only) and assign these roles to the respective users. To prepare the planned integration with the SAP Continuous Integration and Delivery service, create a service instance of SAP Cloud Transport Management and a service key.

The SAP documentation enables SAP Cloud Transport Management including extensive screenshots. The entry point is Set Up the Environment to Transport Content Archives directly in an Application’.

The individual steps are described here:

• Configuring Entitlements to SAP Cloud Transport Management
• Subscribing to SAP Cloud Transport Management
• Setting Up Role Collections
• Creating a Service Instance and a Service Key

The next step is to reflect this landscape in SAP Cloud Transport Management and prepare to connect cTMS to the SAP Continuous Integration and Delivery service.

As an SAP BTP administrator at Rotating Banana, you must set up the transport scenario 'MTA Deployment on Cloud Foundry'.

For this, you create two destinations pointing to your landscape's target subaccounts (test and production).

In the SAP Cloud Transport Management UI, you create three transport nodes (from Dev to Test and from Test to Prod) and connect them with two transport routes (Dev to Test, Test to Prod). This creates a simple linear three-node landscape.

To enable integration with the CI&D service, you provide the SAP Cloud Transport Management service key to the CI&D service, which is stored as a credential.

The SAP Documentation provides details about modeling your delivery landscape in SAP Cloud Transport Management including extensive screenshots. The entry point can be found here: Configuring the Landscape.

The individual steps are described here:

• Create Transport Destinations
• Create Transport Nodes
• Create Transport Routes

The documentation Integration in Development and Change Management Processes and with Other Services provides more information about possible integrations and the details of their setup.

The integration of SAP Cloud Transport Management with the SAP Continuous Integration and Delivery Service (transporting Multi-Target Applications (MTA)) is only one of many possible transport scenarios. SAP Cloud Transport Management is continuously enabled for further content types. The currently supported content types can be found here in the documentation. For example, the list of supported types does comprise content from SAP Build Apps, SAP Datasphere, and SAP Build Process Automation.

You can now perform the steps necessary to reflect your delivery landscape in SAP Cloud Transport Management.

For this, you learned how to subscribe to SAP Cloud Transport Management and how to build your transport landscape from destinations, transport nodes, and transport routes.

Lastly, you gained insights into integrating SAP Cloud Transport Management with other applications, such as the SAP Continuous Integration and Delivery service.

• SAP Cloud Transport Management documentation
• Blog post on integration of cTMS with CI&D service
• Blog post on integration of cTMS with SAP Cloud ALM
• Blog post on integration of cTMS with SAP Solution Manager ChaRm
• Tutorial video series on SAP BTP DevOps including CI&D service, cTMS and Alert Notification service
• Get Started with SAP Cloud Transport Management Service | SAP Tutorials
• Transport SAP Integration Suite Content using SAP Cloud Transport Management Service and SAP Content Agent Service | SAP Tutorials