Skip to Content
Product Information
Author's profile photo Moritz Gysler

Interplay of SAP Cloud ALM and SAP Cloud Transport Management Service

In this blog post I want to explain how to leverage the power of change and deployment management in SAP Cloud ALM in conjunction with the capabilities of SAP Cloud Transport Management Service. By this integration SAP Cloud ALM is capable of supporting the following additional solutions:

SAP Solution Notes
SAP BTP, Cloud Foundry environment

Mainly development content and some selected services. More under Supported Content Types.

SAP BTP, Neo environment

Mainly development content and some selected services. More under Supported Content Types.

SAP Integration Suite

This includes the capabilities Cloud Integration and API Management.

More under Supported Content Types.

Note: SAP Cloud Transport Management will be subscribed automatically in your SAP Cloud ALM subaccount during provisioning of SAP Cloud ALM. Using this SAP Cloud Transport Management tenant in conjunction with SAP Cloud ALM is free of charge. It is not possible to use an existing SAP Cloud Transport Management tenant in conjunction with SAP Cloud ALM.

I will focus on the example of Cloud Integration as part of the SAP Integration Suite. Find more information about how to set up the integration in my blog post Enabling Change & Deployment Management in SAP Cloud ALM for SAP Integration Suite – Cloud Integration. General information about the SAP Cloud Transport Management Service integration with SAP Cloud ALM is available in our SAP Help Portal.

How to utilize features in conjunction with SAP Cloud Transport Management

After you have done the integration you are ready to use features for deploying changes made in Cloud Integration like adding new artifacts to a package. In our example we are preparing an OData service for sales orders.

  • As developer you can start as usual in your Design area within Cloud Integration:

Cloud%20Integration

 

Go%20to%20Design

 

  • Now you can create a new package or select an existing one:

Create%20or%20select%20package

 

  • In the package you can go to the “Artifacts” tab:

Artifacts%20tab

 

  • Switch to Edit mode:

Edit%20artifacts

 

  • Now you can edit an existing or add a new artifact:

Add%20new%20or%20change%20existing%20artifact

 

  • In this example the existing artifact is changed and saved as new version:

Change%20artifact%20and%20save%20as%20version

 

  • Add a comment and confirm by clicking OK:

Comment%20and%20confirm

 

  • Save the artifact change:

Save%20artifact%20change

 

  • Back on the package level the content can be transported:

Transport%20content

 

  • Comment and transport the content:

Comment%20and%20transport%20content

 

  • The Transport ID is created in the configured Cloud Transport Management Service:

Transport%20ID%20created

 

  • In SAP Cloud ALM the transport can be assigned to a feature for deployment. You need to switch to Edit mode:

 

  • The feature deployment can be triggered in Display mode:

 

  • After deployment to production tenant finished successfully the feature can be confirmed:

 

  • In Cloud Transport Management we can see that the transport was deployed to the production environment:

Validation%20in%20Cloud%20Transport%20Management

Wrap-Up

In this blog post you’ve learned how to utilize SAP Cloud Transport Management service in conjunction with SAP Cloud ALM. The chosen example for SAP Integration Suite – Cloud Integration provides a first insight how change and deployment management in SAP Cloud ALM improves your traceability and helps you keeping track of your integration scenarios.

Stay tuned to learn more about orchestrating deployment of your changes for SAP S/4HANA Cloud, private edition and Cloud Integration with one feature.

Looking forward to receiving feedback. For latest updates and notifications you can follow me by clicking Moritz Gysler.

 

Assigned Tags

      8 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Tobias Mache
      Tobias Mache

      Great Blogpost Moritz Gysler 💪🏼

      Author's profile photo Susumu Honna
      Susumu Honna

      Hi Moritz,

      Thank you for your great blog!

      Regarding orchestrating deployment for S/4HANA and BTP you wrote at the end, does this mean that SAP Cloud ALM already support to coordinate transport of related changes between S/4HANA and BTP like it is realized by CTS+ and Cloud TMS?

      Best regards,

      Susumu

      Author's profile photo Harald Stevens
      Harald Stevens

      Hi Susumu,

      yes, that is correct: it is possible to attach Cloud TMS (from BTP) and 'classical' CTS(+) transports (from on premise systems) to one feature. When triggering the deployment both (or several) imports get started synchronously.

      This allows handling of changes in hybrid scenarios.

      Kind regards
      Harald

       

      Author's profile photo Susumu Honna
      Susumu Honna

      Hi Harald,

      Super! Thank you so much for your quick reply!

      The function of Cloud ALM is evolving rapidly!

       

      Best regards,

      Susumu

      Author's profile photo Marcello Urbani
      Marcello Urbani

      What if one of the deployment fails? Is it able to roll back the others?

      Author's profile photo SEBASTIAN Rodriguez
      SEBASTIAN Rodriguez

      Hi Moritz,

      Thank you for your blog!

      I see your note about: "Note: SAP Cloud Transport Management will be subscribed automatically in your SAP Cloud ALM subaccount during provisioning of SAP Cloud ALM. Using this SAP Cloud Transport Management tenant in conjunction with SAP Cloud ALM is free of charge. It is not possible to use an existing SAP Cloud Transport Management tenant in conjunction with SAP Cloud ALM."

      Currently we already have in our BTP CF account a cTMS tenant configured and operational, even integrated with Solution Manager to use ChaRM.

      We are now exploring functions and scenarios with cALM and find that we would not be able to integrate our already operational cTMS tenant with cALM.

      So my queries that I would like to approach both you Moritz and Harald with would be:

      • What alternatives do we have to be able to use cALM also to centralize the cTMS operations?
      • Is there no chance to integrate our current cTMS tenant to cALM?
      • Does everything have to be reconfigured again in cALM with a new cTMS tenant in cALM account?
      • Can the configurations be migrated in any case to have less work?

      Thank you in advance and I remain attentive to your feedback,
      Best regards!

      Sebastian.

      Author's profile photo Harald Stevens
      Harald Stevens

      Hi Sebastian,

      Let’s address your questions:

      • As stated in the blog post, it is currently not possible to integrate an ‘external’ cTMS instance with Cloud ALM. The connection between cTMS and Cloud ALM relies on the two services being in the same subaccount. This might change in the future, but there is no concrete timeline for it.
      • So if you want to control your cTMS transports via Cloud ALM you have to use the cTMS instance in the Cloud ALM subaccount.
      • It is possible to export the complete cTMS landscape from the source instance and import it into the target instance. For this go to the Landscape Visualization and use the Export / Import Landscape buttons:

      Landscape%20Ex-%20and%20Import

      Landscape Ex- and Import

       

      • Unfortunately there is more to do:
        • The cTMS landscape configuration only contains the names of the used destinations, not the destinations themselves.
        • Therefore you have to export the destinations from the cTMS source subaccount and import them into the target (Cloud ALM) subaccount. Unfortunately this is possible only one by one (to my knowledge).
        • For security reasons the passwords inside the destinations are not exported and have to be entered again in the target subaccount for all destinations
      • Last not least, you have to adopt the destinations / configurations where cTMS is called from other applications, for example the destination ‘TransportManagementService’ when using the Cloud Integration (Suite) scenario. Please note that the destination looks somewhat different because the calls to cTMS are routed through Cloud ALM. See for example: https://blogs.sap.com/2022/05/04/enabling-change-deployment-management-in-sap-cloud-alm-for-sap-integration-suite-cloud-integration/

      So all in all, migration is possible, but connected with some (one time) work.

       

      Kind regards
      Harald

       

      Author's profile photo SEBASTIAN Rodriguez
      SEBASTIAN Rodriguez

      Hi Harald,

      Thank you very much for your prompt answers and clarifications regarding the use of cTMS in conjunction with cALM, and the path we would have to take to migrate the cTMS settings to the cALM service.

      We will take this into account and use it as a guide to face the adoption of cALM in our Organization.

      Kind regards 😊!

      Sebastián.