Error while transporting CPI package using TMS

[prabalrakshit]

Dear All,

We are trying to move CPI iFlow packages from one tenant to another using Cloud Transport Management Service. We have been following the process described in

https://help.sap.com/docs/cloud-integration/sap-cloud-integration/enabling-content-transport-cloud-f...

In summary we have done:

1. The source and target destination setups

2. Necessary access to transport iFlows

3. The CTMS Nodes and routes

However on attempting to transport a package from the source to target tenant, we see an error as follows:

Transport request 'MyTestPackage - Transport' (id: 424): Exception during start of deployment for deploy type 'SLP_CTS': Start of deployment failed: Operation 'Create Deploy Resource' to the URL 'https://content-agent-engine.cfapps.us10.hana.ondemand.com/cas/gacd/v2/deploys' failed. Remote server responded with HTTP status code 400, response body: '{"errorType":"CASGACDBadRequestException","error":"Only One content allowed."}'

The target node for the route has been configured as mentioned in https://help.sap.com/docs/CONTENT_AGENT_SERVICE/ae1a4f2d150d468d9ff56e13f9898e07/06bd9e2d55084eaf923....

We have created an instance of content agent service in the target tenant and used its service keys to set up the target CTMS destination.

Any suggestions on what we may be missing here?

Regards,

Prabal

[Harald_Stevens]

Hi Prabal,

the error message seems to indicate that there is more than one content file attached to the transport request. Normally this should not happen when creating the transport request from within Cloud Integration.

Did you use a special process to create the transport request?

Kind regards
Harald

[prabalrakshit]

Hello Harald,
Thanks for the reply. I created the transport request through the Transport option in Cloud Integration cockpit. I was trying to push an iFlow package to another tenant. The MTAR file was not created manually.

Is there anyway I can check if there is more than one content file attached to the transport request?

Here is a snippet of the log

transportlog431.txt