Transport SAP Cloud Integration (CPI) Artifact with SAP Cloud Transport Management

[syedkamran]

Introduction:

SAP Cloud Transport Management is a multi-tenant aware application that not only streamlines the handling of development artifacts and application-specific content but also ensures tenant separation. This means you can efficiently manage software deliverables between accounts in different environments (such as Neo and Cloud Foundry) on SAP BTP, securely transporting them across various runtimes while maintaining a clear distinction between tenants.

Pre-requisites:

Subaccount -

-- Three Integration Suite Subaccount (Alias DEV, QAS and PRD) respectively

a.  Enable Cloud Foundry environment ad create space,

b.  Entitlement Access :

b.1. Integration Suite (enterprise_agreement or free)

b.2. Process Integration Runtime (integration flow and api)

-- One Cloud Transport Management Subaccount (Alias CTM)

a. Entitlement Access :

a.1. Cloud Transport Managment (standard)

a.2. Content Agent Service

 

Configuration Steps :

Goto Develoment Integration Suite Subaccount (DEV).

 

Click on Service --> Instance and Subscription --> Create.



 

Choose Service : Integration Suite, Plan:Enterprise_agreement.

 

Assign the Role Collection Name : Integration_Provisioner.

 

Goto to Integration Suite Application and activate the Cloud Integration Manage Capabilities.

 

Again Click on Service --> Intance and Subscription --> Create.

 

Choose Service: Process Integration Runtime, Plan: api, InstanceName : cpi-dev-i



 

In the next Type Select Grant_Type : Client_Credentials and Roles: WorkspacePackagesTransport and click Create.

 

Now create the service key with the default option and name for Process Integration Runtime Instance.

 

Goto Cloud Transport Management Subaccount.

 

Click on Service --> Instance and Subscription --> Create.



 

Choose Service : Cloud Transport Management, Plan:standard.

 

Assign the Role Collection Name : AuthGroup.Administrator.

 

Again Click on Service --> Intance and Subscription --> Create.

 

Choose Service: Cloud Transport Management, Plan: standard, InstanceName : ctm-i

 

Also create the service instance for Service : Content Agent Service, Plan : Standard, Instance Name :  cas-i

 

Then create the service key for Cloud Transport Management & Content Agent Service instance respectively.

 

HTTP Destination from DEV subacccount pointing to Content Agent Service Instance.

Field	Description
Name	ContentAssemblyService
Type	HTTP
URL	Provide URL from service key
Proxy	Internet
Authentication	OAuth2ClientCredentials
Client ID	Provide uaa client ID from the service key.
Client Secret	Provide uaa client secret from service key
Token Service URL Type	Dedicated
Token Service URL	Provide uaa url from service key and add in the last /ouath/token

HTTP Destination from Cloud Transport subaccount to PI Integration runtime (api).

Field	Description
Name	CloudIntegration
Type	HTTP
URL	Provide oauth URL from service key and add in last /api/1.0/transportmodule/Transport
Proxy	Internet
Authentication	OAuth2ClientCredentials
Client ID	Provide oauth client ID from the service key.
Client Secret	Provide oauth client secret from service key
Token Service URL Type	Dedicated
Token Service URL	Provide oauth token url from service key.

 

Three HTTP destination from Cloud Transport Management subaccount point to DEV, QAS and PRD subaccount respectively

Field	Description
Name	DEV
Type	HTTP
URL	https://deploy-service.cf.eu10-004.hana.ondemand.com/slprot/<cf-org>/<cf-space>/slp
Proxy	Internet
Authentication	Basic Authentication
User	Specify the name of the technical user that is used for the deployment.Technical User must have space developer role.
Password	Specifiy the password  fo of technical user

 

Login to the Cloud Transport Management

 

Navite to the option Transport Node and then Click on + .

 

To define the source transport node provide Name, Description and check the option "Allow Upload to Node. Rest leave everything as default.

 

Create new transport node with following shown and leave rest everthing default for Quality and Production respectively.

 

Navigate to the transport route option ,Click on +.

 

 

Now mention the transport route name, Choose source node as DEV and target as QAS.

 

Now create the new transport route for QAS and PRD as shown.

 

Navigate it to Landscape visualization and note the name of source node as shown below in point 2.

 

• HTTP Destination from Cloud Transport subaccount to Cloud transport Management Instance.

Field	Description
Name	TransportManagmentService
Type	HTTP
URL	Provide uri URL from service key
Proxy	Internet
Authentication	OAuth2ClientCredentials
Client ID	Provide uaa client ID from the service key.
Client Secret	Provide uaa client secret from service key
Token Service URL Type	Dedicated
Token Service URL	Provide uaa url from service key and add in the last /ouath/token
Additional Properties	Name : sourceSystemId Value :Enter the ID of the source node of the transport route

 

Configure the transport mode in Integration suite. Navigate to Integration Suite Development (Go Application) --> Setting --> Transport and Choose Transport Mangement Service.

 

Now Click on Check Configuration button to check that all the configurations are correct.

 

Testing Steps:

 

To transport the desired package , click on button Transport available on the top left side of screen.

 

Fill in the comment in the space and click on Transport.

 

If the export of the package content is sucessfull.Then the below message will be displayed.

 

To import the transport in QAS, Login into the Cloud transport tenant Click on Transport Node, Select the QAS Node, then select  the transport Request and click on button Import Selected.

 

Status of the transport can be can be monitored from column status.

Reference --

SAP Help Portal - https://help.sap.com/docs/cloud-transport-management/sap-cloud-transport-management/administration