SAP Cloud TMS Node controlled by SAP Solution Manager

[T1mey]

Hello @all,

we have a question about SAP Cloud TMS.

We own an Azure Devops Pipeline which does the following for manual transport (à no ChaRM integration).

1. We are deploying the application directly to the DEV system
2. We upload the build mtar to the import queue of the QA SubAccount

Now we want to use ChaRM as a transport tooling. So we created a new deployment route.

The configuration of the QA Node (and PROD node) is

As we wanted to stick to the logic above which is used in the manual process (import the mtar to QA queue) we’re trying to upload it and getting an exception.

error tmsUpload - HTTP request failed with error: request to https://transport-service-app-backend.ts.cfapps.eu10.hana.ondemand.com/v2/nodes/upload returned with response 422 Unprocessable Entity
error tmsUpload - Response body: {"message":"Node is controlled by SAP Solution Manager. The operation can be triggered by the controlling application only","errorType":"com.sap.lm.sl.alm.ts.core.exception.service.TsUserReportableException"}

As the option "Upload Allowed" is set this doen't seem to be right.It would make no sense to upload to the DEV node (set not controlled by SAP solman).Any ideas?

[Harald_Stevens · Accepted solution]

Hi Tim,

the 'controlled by Solution Manager' flag 'wins' over the 'Upload allowed' flag.

So you have two options:

1. You remove the 'controlled by SolMan' flag from the QA node.
   Advantage: easy to apply
   Disadvantage: imports could be initiated manually from the cTMS UI
2. You create a dummy DEV node before the QA node and connect it with a transport route with QA.
   Settings: 'Upload allowed' yes, 'Controlled by SolMan' no.
   You don't need a destination for the DEV node.
   In your Azure pipeline you replace the 'upload' call with the 'export' call:
   https://www.project-piper.io/steps/tmsExport/
   and do the 'export' from the DEV node. This places the transport request into the QA queue ready to be picked up by ChaRM. You can remove the 'upload allowed' flag from the QA node.

I would prefer the second option, even though it takes a little more effort to implement.

Kind regards
Harald

[T1mey]

harald.stevens Thanks a lot ! Option 2 is doing what we wanted to achieve !