Technical Articles

Sabarish T S

September 13, 2017 2 minute read

CTS+ based Transport in Cloud Platform Integration

With the September 2017 monthly releases of Cloud Platform Integration customers have the option to transport Integration Packages across Tenants using CTS+ based system.

If you are an organization using SAP’s CTS+ On-premise system and have two Cloud Platform Integration tenants test and production and would like to design and test an integration flow only on the test landscape. In such a situation the new transport feature enables you transport the integration package from the test to the production landscape via your central transport environment CTS+.

The existing mechanism of transporting using manual export and import continues to be supported.

Settings to be done to enable CTS+ based transport

You should enable transport to CTS+. As a Tenant Admin (having Tenant Admin Role) you can do this by accessing Settings Option and choosing the tab Transport Settings. You would have to choose either ‘MTAR Download’ or ‘CTS+ Direct’ from the dropdown list.
Enable the service, Solutions Lifecycle Management in your account. Ensure that you perform this step in all the accounts where you want to use content transport using CTS+. This is a one-time activity. You can do that by
1. Login to your account in the SAP Cloud Platform.
2. Choose Services Solutions Lifecycle Management .
3. Choose Enable.
Create a new HTTP destination by selecting Configure Destinations. Ensure that the Name of the destination is CloudIntegration (case-sensitive) and the URL is the URL of the tenant management node

Note:

This is the source system Tenant URL in our example Test Tenant URL from which you want to transport content. The Tenant Management URL can be obtained from the accounts cockpit which lists the applications that are subscribed.
The user credentials that you have used in the destination should be a member of the tenant management node account from which you want to transport content.
Ensure that this user that you are using for authentication has the Role IntegrationContent.Transport

Ensure that all Integration developers who would be transporting content have the Role IntegrationContent.Transport

Transporting the Content using CTS+

The mtar file

In the Source Tenant select the integration package that you want to transport.
Choose Transport. This option is available if you have done Setting 1 and 4 above.
In the Transport Comments prompt, provide comments and choose Transport.
A file with extension mtar is downloaded to your local file system in the download path configured in your browser. This would happen if you have chosen ‘MTAR Download’.
If you have chosen ‘CTS+ Direct’ then based on your configuration the transport object would be attached to your open transport request.

Importing the mtar in CTS+ and releasing it / importing it from import queue to Target Tenant

Configure your Application Type for Cloud Platform Integration.
Configure the transport landscape
Attach the mtar file to your transport request and release the request to your target system. This would be required if you are using the option ‘MTAR Download’.
Import the transport request with the Integration Package content into your target system.

Refer to blog Content Transport using CTS – Cloud Integration – Part 1 for more details.

Refer the documentation Change Management with CTS+ for more information.

13 Comments

You must be Logged on to comment or reply to a post.

Ashish Goel

September 13, 2017 at 8:35 am

Nice feature added in CPI. Do we need to transport complete package every time or we can transport just i-flow as well.

Also, where can we see transports history.

Thanks,

Ashish

Rajasekhar reddy

November 8, 2017 at 11:32 am

Dear Ashish,

Did you got any information for above mentioned query? If yes please let us know..

Thanks and Regards,

RAJA

Ashish Goel

November 21, 2017 at 8:47 am

Hi Raja,

I didn't get any information as of now about how to check transport history.

Regarding transporting individual objects , yes it is possible. Check this blog as well.

https://blogs.sap.com/2017/11/20/cts-finally-in-sap-cloud-platform-is/

Thanks,

Ashish

Rajesh Kumar

September 13, 2017 at 9:50 am

Hi Sabarish - Thanks for sharing the above new feature availability in SCP.

Is the version of tmn should be 2.31.8+ for using this feature?

Where we can get the document link for this feature for knowing more details.

Thanks & Regard

Rajesh

Amarendra Gangulakunta

September 20, 2017 at 4:03 am

Hi Sabarish,

I am getting the error "Unable to fetch the status of MTAR file creation" while exporting the Integration content artefact by using the 'Transport' button over there. Any idea what could be the reason?

Thanks & Regards,

Amarendra.

Former Member

October 18, 2017 at 8:28 am

I'm also getting the error "Unable to fetch the status of MTAR file creation". Were you able to solve this error?

Thanks!

Michaël

Rajasekhar reddy

November 8, 2017 at 11:34 am

Hi Amar and Michael,

I’m also getting the same error “Unable to fetch the status of MTAR file creation”. If you found any solution for this please help me..

Thanks in advance..

Regards,

RAJA

Hari Sonnenahalli

November 20, 2017 at 10:44 pm

All-

Please find the updated blog below which provides a stepwise configuration to fetch mtar file.

https://blogs.sap.com/2017/11/20/cts-finally-in-sap-cloud-platform-is/

Regards

Athar Iqbal

February 23, 2018 at 2:38 am

Hi Hari,

I followed all the steps in your blog on TEST tenant to transport artifacts from TEST to PROD. When I tried to transport the package or even individual flow, it errors out saying

"Could not export package; Artifact(s) have working copy"

Any idea why? My S-ID is part of the administrator group. I have added transport role as well just to be on safe side.

I have created the connection and tested it, it came back with status code 200 OK.

Sabarish T S

Blog Post Author

March 15, 2018 at 10:13 am

You can only tranport a package which has content with a defined version. So please use Save as Version option and ten try again. If the content is in Draft state you would possibly get this error

A D

October 1, 2018 at 1:07 pm

Hi,

I am trying to transport SAP CPI package using CTS+. I have followed the documentation & I am able to see the MTAR file attached in the transport request generated using CTS system. However when I import this transport request in the target CPI tenant, the transport ends up in return code 4(warnings are not shown) & the integration package does not appear in the target CPI tenant.

The connection test is also successful in SM59. Please advise.

Saicharan Srinivasan

October 22, 2018 at 7:25 am

Even i am facing the same issue , can you please let me know, whether you got any updates for the solution ?

Hans-Dieter Frey

September 22, 2022 at 7:56 am

In this case you may want to check STMS configuration of CTS+ target system: Typically RC=4'/'Warning' reflects missing (or incorrect) target system resp. DeployURL configuration.

So please check whether required deploy method (for correct application type, no typos allowed -and case-sensitive) is configured in STMS for CTS+ target system (Goto -> Application Types -> Deployment Method). Output of TransportTool Check(/report RSTMS_NONABAP_SUPPORT) for CTS+ target system may give further indications on issues...

Regards/HTH,

Hans-Dieter (CTS+)