Skip to Content
Product Information

SAP Cloud Platform Transport Management service generally available

Beta phase completed

After a successful closed beta testing phase (see The new cloud-based Transport Management Service) we have shipped the first generally available productive version of SAP Cloud Platform Transport Management service (TMS) on 22nd of November 2018.

Overview

TMS is a purely cloud-based solution for transporting development artifacts or application configuration content between SAP Cloud Platform subaccounts (respectively Cloud Foundry spaces). The sources and targets for the transportable content are modeled inside TMS as transport nodes and connected via transport routes. With these parts you can setup your transport landscape(s). These landscapes can of course be more complex than the standard three system landscape shown below. The content is attached to a transport request which is then moved along your transport routes and deployed to the corresponding target accounts.

TMS currently supports the SAP Cloud Platform Neo and Cloud Foundry environments as transport nodes (Neo subaccounts and Cloud Foundry spaces). The content can be Multi-Target Applications (MTA), SAP Cloud Platform Integration (CPI) packages and SAP HANA delivery units (DU), if the HANA database is hosted in SAP Cloud Platform.

Boundary Conditions

SAP Cloud Platform Transport Management service itself is running in the Cloud Foundry environment and in order to use it you need to subscribe to it from one of your own Cloud Foundry subaccounts. Currently this subaccount has to reside in one of the Amazon Web Service data centers in either Europe (Frankfurt) or US East (VA). The target subaccounts for transporting can reside in any data center and cross-region transport is possible.

Pricing

TMS will first be offered in a consumption-based pricing model at currently 18 EUR per used GB bandwidth of data uploaded to the service per month. This can be paid with Cloud Credits which can be used for all SAP Cloud Platform services offered in this pricing model.

From 2nd of April, 2019 it is also possible to subscribe to TMS via the SAP store, please see the corresponding blog by my colleague Boris Zarske. The services details page of TMS in SAP store can be found here.

NEW: Transport Management service is now available in a trial version. See this blog for more information.

For further information please check https://cloudplatform.sap.com/pricing.html.

Further Information

Check out the introductory video on TMS.

There is extensive documentation available including a bunch of videos showing the setup of TMS step by step.

Outlook

We will continue to further develop TMS, e.g. by opening TMS to new SAP Cloud Platform environments and new services within SAP Cloud Platform. At SAP TechEd Barcelona 2018 we also tested a graphical display of the transport landscape which has been rolled out in a recent version of TMS (see screenshot below).

 

18 Comments
You must be Logged on to comment or reply to a post.
  • Hi all, for CPI, will there be special handling regarding exchange of target system landscape much as SLD and integration directory does on on Prem PI? Or do you solely rely on externalized parameters for such?

     

    Cheers

    Jens

    • Hi Jens,

      the behavior for CPI content transported via TMS is identical to a manual export and import of an integration package. So there is no special handling as you asked for in your question.

      However, as a (non-binding…) outlook: we are planning to introduce configurable pre- and post-import actions for TMS. Those could include CPI specific activities provided by the CPI development team.

      Kind regards
      Harald

      • Thanks Harald. Sounds interesting. I would suppose this feature would (if it comes to happen) then differentiate TMS more from CTS+ (other than when heading towards “serverless” I would want to use TMS anyways).

        Cheers

        Jens

  • Hi all, I have two questions about TMS:

    1. Is it possible to transport from a tenant in a Global Account (based on subscription model) to a tenant in another Global Account (based on CPEA)?
    2. Is it possible to transport everything that I have developed in terms of code and services, or there are services that is not possible to transport

    Thanks, Paolo

    • Hi Paolo,

      let me try to answer your questions:

      1. Is it possible to transport from a tenant in a Global Account (based on subscription model) to a tenant in another Global Account (based on CPEA)?
        Yes, the license type is not relevant for the subaccounts modeled in TMS. You can transport between different global accounts. They can even reside in different data centers (of course with increased network latency…).
        Only the Cloud Foundry subaccount from which you subscribe to TMS has to be (as of 26th of February, 2019) CPEA based (and currently located either in Europe or US).
      2. Is it possible to transport everything that I have developed in terms of code and services, or there are services that is not possible to transport
        Currently all generally available scenarios are based on Multi-Target Applications. So in that sense everything that can be put into an MTA can be transported. For the currently supported artifacts in an MTA see here for Cloud Foundry and here for Neo.
        As you can see from the list of artifacts this mainly relates to development content like HTML5 applications or nodeJS modules. This covers by far not all available services in SAP Cloud Platform.
        The architecture of TMS allows the transport of application / service specific content, but this has to be implement on a ‘by service’ level, which means that each service has to implement some APIs that TMS provides. This has been done so far by Cloud Platform Integration (CPI) and other services are currently doing it.
        So in the moment the answer is that most services are not fully supported by TMS.

      For us it would be very important to learn which services would be most relevant for being TMS enabled so that we can prioritize our efforts accordingly.

      Kind regards
      Harald

  • Transport diagrams and change SDI connection?
    Actualimente solo tengo una cuenta de SCP y en la base de datos tengo creado un esquema con una conexion SDI a ERP QAS. Es posible que en la misma cuenta en otro esquema PROD se puede transportar lo del esquema anterior y acabiar la conexion SDI a ERP PRD?
    • Hello Ashmita Sinha,

      I hope I understood your question correctly.

      Yes, it is possible to transport content between CF spaces with TMS. There are two differences compared to the configuration in Neo:

      The default scenario in CF would more or less look like that:

      • In your development space you create an MTA project in WebIDE
      • After completion of the project you build the MTA from within WebIDE
      • You export the MTA archive file to your local drive from within WebIDE
      • in TMS you create a new transport request targeting your test space
      • You attach the downloaded MTA archive to the transport request
      • You import the transport request into the test space
      • The transport request is automatically forwarded to the next space on your transport route, e.g. the productive space
      • You import the transport request into the subsequent space(s)

      We are planning within Q3 also to enable integration of TMS into a CI/CD process, which would automate most of the above steps.

       

      Kind regards

      Harald

       

  • Hello Harald,

     

    We are building a SaaS solution, I tried to use the transport management service in our globale account but failed. What I did is following:

    1. We have an global account on Canary landscape and several subaccounts.
    2. I changed the entitltment of our global account with service of: Transport Management and Transport Management DEV Service and alocate the quota to one of our subaccount.
    3. When I check the subsptions of my subaccount, I could not see the service available on the subscriptions.
    4. When I look into my subaccount space, I could see two services in the ‘Service Market Place’: Transport Management (transport) and Transport Management (transport-dev). In the description, it shows as:” Provides programmatic access to SAP Cloud Platform Transport Management service that lets you manage transports between SAP Cloud Platform accounts in Neo and Cloud Foundry, such as from DEV to TST and PROD accounts”. It allows me to generate a new instance, in in the new instace I could bind applications.

    The above steps are quite different with what you describe here, could you help to let me know what step I missed?

    In addition, for the transport management, could we do following:

    1. Transport the content from Canary Landscape (global account 1) to Factory Landscape(global account 2)?
    • Hi Radar,

      normally this should work 😉

      To all external (non-SAP) readers: we talk about the SAP internal Canary landscape which is not accessible from the outside. However, the steps described here are the same for the ‘real’ (factory) environment.

      Let’s double-check the steps:

      1. in the CF subaccount you want to run TMS in, Cloud Foundry is enabled (an organization exists)?
      2. The entitlement for TMS in the global account looks like this (the subaccount name here is ‘Harrys Home’)?

        You only need the entitlement for Transport Management, the one for Transport Management DEV is the newest internal build, might still contain bugs and will very frequently be updated…

      3. In the subaccount on the subscription tab you find Transport Management?

        You have to be a member of the global account in order to see (and change) the subscriptions on subaccount level.

      4. The service instance you mention is needed for setting up the so called ‘close coupling’. This means that TMS is called from an application to create a transport request and attach content to it. Currently this is available for SAP Cloud Platform Integration (CPI) in Neo environment and for the Solution Export Wizard (also on Neo). Please see Set Up the Environment to Transport Content Archives directly in an Application on SAP Help for details on the configuration and use.
        The fact that you see the two services in the ‘Service Market Place’ indicates that entitlement has worked.

      As for your last question: in order to transport from Canary to Factory subaccounts TMS has to run on the Canary landscape. As you plan to do this, the intended scenario should work.
      It would not be possible to import into a Canary subaccount from a TMS running on Factory.

       

      Hope that helps.

      Kind regards
      Harald

       

      • Hi Harald,

         

        Thanks for the details, I am the global account admin, but I could see the subsription tile for the ‘Transport Management’.

         

        Is there any other specific role or setting required?

         

        Thanks and best regards,

        Radar

         

        • Hi Radar,

           

          I suppose you wanted to say that you could not see the Transport Management tile, right?

          I am not aware of any additional role or setting needed.

          The only advice I could give is to clear the browser cache and reload the subscriptions page.

           

          If this doesn’t help I would suggest to follow up that issue SAP internally. If something important comes up during our investigation I would post it here.

           

          Kind regards
          Harald

           

  • Hi Harald,

    thank you for the nice summary. I already asked this on an older article but: will it be possible to transport single integration artefacts or just the whole package?

     

    Thank you and best regards

    Matti

    • Hi Matti,

       

      unfortunately the situation has not changed: the transport of SAP Cloud Platform Integration artefacts still happens on package level.

      I will mention your requirement to the CPI development team and hope they might consider it…

       

      Sorry and kind regards
      Harald