SAP Cloud Integration – Transport at Artifact Level
SAP Cloud Integration version 5.23.**/6.15.** comes with enhancement in transport, where in you can transport single or multiple artifacts rather than the entire integration package.
- The forecasted SAP Cloud Integration customer tenant software updates/availability of this version is planned for calendar week 27/28’ 2021 as per the phased tenant update procedures, which may be subjected to change.
- Know-how of SAP Cloud Integration Transport is required to get insights of this blog.
Transport in SAP Cloud Integration is one of the basic needs to move the integration content between different tenants, mostly marked as development, testing and/or production tenants. Till date, the transport of integration content was at the integration package level. So, even if you change/update one or few integration artifacts, then it was required to transport the entire integration package.
With introduction SAP Cloud Integration Transport at Artifact level, no need to transport the entire package, you can now transport only changed/updated artifact(s).
This blogpost covers only the enhancement, and not the complete transport story, especially the configuration part of it, which you can find in the document https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/e3c79d65aa604b80992e20609881ad7a.html and blogs like https://blogs.sap.com/2018/04/10/content-transport-using-cts-cloud-integration-part-1/ and relevant. The setup(for the different transport modes like MTAR Download, CTS+ Direct and TMS) remains same as for the package level transport.
Single artifact Transport
The Transport action is now introduced at artifacts list viewer of the integration package, sample screenshot below
Multiple artifacts Transport
If you have more than one changed/updated artifacts, you can use multi-select option and the transport action as showcased below.
As you might have noticed the description text of the transport dialog, though the transport is happening at the artifact(s) level, underneath the package information is captured and created/updated accordingly in the target tenant, because, artifact on its own can’t sit in a tenant and it needs integration package (as container) in the tenant. Transport of artifact(s) in DRAFT state is/are not supported.
- Access Policies : If an artifact is protected with access policies in source tenant, then transport of such artifact is not possible. Update : access policy checks are not done during the transport at target tenant hence the line -> And at target tenant, other artifact(s), which is different from artifact getting transported from source, is/are protected with access policies in target tenant, then the transport of such artifact would not succeed. We will be addressing this issue in our next releases. <- are not relevant. To know more about access policies, you can check blog at https://blogs.sap.com/2021/06/07/access-policy-for-securing-design-artifacts-and-control-access-to-integration-flow-in-the-sap-cloud-integration/
This enhancement in transport, the overhead of transporting the entire package for the changes in one or few integration artifacts gets reduced. You can only transport the artifact in need.