Product Information
SAP Cloud Platform Transport Management roadmap as of June 2020
Dear fans of SAP Cloud Platform Transport Management,
I would like to provide you with the brand-new (as of mid of June 2020) roadmap for our product. As a roadmap is a forward-looking statement I have to start with a disclaimer, that the plans mentioned below can change at any time. The more formal disclaimer can be found at the end of this document.
Roadmap
TMS roadmap as of June 2020
Recent Highlights
I would like to point out three items which have become available recently:
- The support of Multi-Target Application (MTA) extension descriptors in the Cloud Foundry environment makes it possible to add node specific configuration settings to the deployment of an application. That could be interesting if you for example would like to assign a different number of resources for your application in the test and the productive environment. Please see the documentation here.
- Transport Management now delivers attributes for the role templates TransportOperator, ExportOperator, and ImportOperator. You can use the attributes to restrict the authorizations of a role to specific transport nodes only. For details see the Security chapter of our documentation.
- We have greatly improved the data center coverage of transport management. It is now available in nearly all AWS and Azure data centers hosting SAP Cloud Platform.
Please also check out the What’s New section in our documentation.
Upcoming Development
From the development we have planned for the next weeks and months I would like to point out two items:
- With the support of blue-green deployment of MTAs in the Cloud Foundry environment we plan to enable zero downtime delivery of new versions of applications, if they are compatible with this procedure.
- The automated import will be a node specific setting triggering an import every time a new transport request enters the import queue.
Call for Action
If you see something you like or miss something you urgently need please let us know by adding a comment. Thank you very much in advance.
Disclaimer
SAP has no obligation to pursue any course of business outlined in this blog or any related document, or to develop or release any functionality mentioned therein.
This blog, or any related document and SAP’s strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this blog is not a commitment, promise or legal obligation to deliver any material, code or functionality. This blog is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This blog is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this blog, except if such damages were caused by SAP’s intentional or gross negligence.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
Hi Harald,
Thanks for the updates!
Just a question regarding API Management. I saw that the content transport is planned to be available on Q4/2020, so currently there is no option other than manual export/import?
Do you have more details on how the functionality will work for API Management service? It will be similar to what we already have in CPI?
Best regards, take care,
Leonardo
Hi Harald:
Since mtar file type is only supported for TMS upload and import for now and I do not see a scheduled timetable for other application content.
Just want to clarify how it is supported for wrapping jar/war file to mtar file.
If original Java project like this:
<PROJECT-ROOT>/
|– application/
|– src/main/java/
`– src/main/resources/
|– integration-tests/
|– src/test/java/
`– src/test/resources/
`– unit-tests/
|– src/test/java/
`– src/test/resources/
Does it mean I have to change project structure to following to support mta upload for TMS?
<PROJECT-ROOT>/
|– srv
|– application/
|– src/main/java/
`– src/main/resources/
|– integration-tests/
|– src/test/java/
`– src/test/resources/
`– unit-tests/
|– src/test/java/
`– src/test/resources/
`– mta.yml
Is there a way for me not to change original Java project but add one more mta description file for mta deployment only?
Hello Harald,
thank you for the Roadmap updates, it’s really useful!
I noticed that in the official documentation there is no explanation on how to achieve the close coupling approach while transporting MTAs between Cloud Foundry subaccounts.
It seems that this approach is only applicable to SCPI (NEO) and MTA (NEO), while in CF only loose coupling with manual MTAs upload is available, otherwise you need CTS+ with on-prem systems.
Is it correct? Will close coupling be implemented also for MTA (CF) in the future?
Thank you
Regards
Hi Harald,
When can able to do iflow transports (CF-TMS) individually instead of whole package?