Overview 

We will discuss configuration of SAP BTP Transport Management Service (TMS) with various BTP services.  Additionally, we’ll discuss integration of SAP TMS with ChaRM, which provides a one-stop shop to manage all transports created from various services on BTP. 

Initial Setup for SAP Transport Management Service 

To setup the SAP TMS instance, we will need to perform the below activities. 

• Configuring Entitlements for Cloud Transport Management 
• Subscribing to Cloud Transport Management 
• Setting Up Role Collections 

• Creating a Service Instance and a Service Key 

Detailed steps to perform each of these activities are available here at Setup TMS Instance.  

Configure Landscape  

Before we can use SAP TMS to transport applications or other developments created in various services between different subaccounts, we must configure the landscape.  

To configure the landscape, we’ below steps: 

• Create Transport Destinations. 

• Create Transport Nodes 

• Create Transport Routes 

• Create Destinations from BTP applications to SAP TMS. 

To perform these steps, we can either use the inbuilt landscape wizard or manually configure the individual entities. For this blog, we will use the landscape wizard. 

Before proceeding to the next configuration, we will be creating Transport Destinations in BTP cockpit Connectivity à Destinations. Destinations contain the address of the target end point as well as the user credentials of the platform user that we need for the destination. 

We must point this to deploy the service of development space.  

Similarly, we will be creating a destination pointing to the Test and Prod tenant. 

Next, we’ll proceed to the Landscape Wizard and will define the following: 

• Transport Nodes: In Cloud Transport Management, transport nodes represent the source and target end points of a deployment process, such as a Cloud Foundry subaccount. Transports take place between transport nodes. This can be a free text, but since we’re going to integrate these nodes with Charm, we’ll keep these names at a maximum of three characters as per SAP’s recommendation. 

• Allow Upload: This should be checked only for the node in which we want files to be directly loaded to the node. 

• Forward Mode: This value is set to Auto. When the import of a transport request is started, the request is automatically forwarded to the target transport nodes according to the transport routes defined for the node where the import started. If we want to manually forward transport requests for this node, set Forward Mode to Manual. 
• Destinations: We must point nodes to the end point destination we created in the previous step. 

Transport Routes: In SAP Cloud Transport Management, transport routes are used to connect transport nodes. 

This concludes the initial configuration of TMS service.  

Next, we’ll discuss the steps to integrate TMS to CPI service to import artifacts from one tenant to another. 

Integration of TMS with CPI 

We need to create destinations in our SAP BTP subaccount to transport integration packages from a source tenant to the target tenant. 

The following two destinations must be created: 

• ContentAssemblyService 
• CloudIntegration 

Please note the destinations should be the same and are case sensitive, so create the destinations as per the step mentioned in SAP help Doc. 

Once created, we will navigate to CPI tenant and change Transport Mode to “Transport Management Service” and click on Check Configuration to check the status of integration. We should get a successful integration message as per below screenshot. 

Integration of TMS with Charm 

There are different steps to configure in Solution Manager and BTP TMS for this integration. 

Solution Manager:  

• Create RFC connections to Transport Management: Below RFCs need to be created in solution manager system to connect with the TMS instance.

1. RFC destination for SAP Cloud platform TMS authentication – CLOUD_TMS_AUTHENTICATION 

1.  RFC connection for the SAP Cloud Platform TMS REST APIs – CLOUD_TMS_API 

• Create external service systems for the Transport Management nodes.

1.  In LMDB, we must create an external service system to represent the transport nodes in the SAP Cloud Platform Transport Management service and assign below attributes. 

• Cloud TMS Node: X 
• Cloud TMS Node Name: The transport node name, such as NE1. 

• Cloud TMS Authentication RFC: The dedicated RFC, such as CLOUD_TMS_AUTHENTICATION. 
• Cloud TMS REST API RFC: The dedicated RFC; for instance, CLOUD_TMS_API. 

• Create a change cycle with the solution landscape:  Create a change cycle as per the standard SAP recommendation to follow a workflow for change deployment.

Detailed steps can be found in SAP note. 

BTP TMS Configuration 

In SAP TMS Landscape we must edit the nodes and select the nodes to be managed by Solution Manager. 

These are all the steps required to configure TMS with CPI and Charm. This integration it makes easy to manage a hybrid landscape. We can leverage all the benefits and best practices we have in a standard S/4 system. 

I hope this helped in getting an overview about TMS setup and integration. Please leave a comment and your feedback on this blog as it will help me grow.  Follow my profile for related content.

Additionally, please follow SAP Business Technology Platform environment Topic page https://community.sap.com/topics/business-technology-platform, post and answer questions https://answers.sap.com/tags/8077228b-f0b1-4176-ad1b-61a78d61a847, and read other posts on the topic https://blogs.sap.com/tags/8077228b-f0b1-4176-ad1b-61a78d61a847/