
Series – TMS:
The following sample configuration describes the scenario: Transport of Content Archives that are available on Local File Systems.
The content archive (.mtar files, for example) has been downloaded or exported from an application in the source DEV subaccount to a local file system. It is then manually uploaded to the import queue of the TEST node in SAP Cloud Transport Management so that it can be deployed to the TEST subaccount and further transported to PROD Node.
Cloud Transport Management | standard | Service |
Cloud Transport Management | standard (Application) | Application |
Cloud Foundry Runtime | memory | Service |
Please follow this guide to set up your TMS environment : https://help.sap.com/viewer/7f7160ec0d8546c6b3eab72fb5ad6fd8/Cloud/en-US/25a3bb93c6334c7780c8f65b0c3...
Transport destinations (for deployment) needs to be set for each node which is planned to deploy the application. In this scenario, we should configure transport destinations for both TEST Node and PROD Node.
In SAP BTP Cockpit of the subaccount with TMS provisioned, choose Connectivity -> Destinations -> New Destination.
Fill in with the following information:
FieldValueDescription
Name | TEST_Node | For example. |
Type | HTTP | |
URL | https://deploy-service.cfapps.<default-domain>/slprot/<myorg>/<myspace>/slp. | As a result, the MTA is deployed into the space <myspace> of the organization <myorg>. The default domain can be found in the API Endpoint. For example (BTP@AliCloud): https://deploy-service.cfapps.cn40.platform.sapcloud.cn/slprot/beta-support_testagain-75bwmerz/tms/s... |
Authentication | BasicAuthentication | |
User | Specify the name of the technical user that is used for the deployment. The technical user used for the destination must be a valid user on Cloud Foundry environment, and it must have the role SpaceDeveloper in the target space. | |
Password |
For example:
Click Save.
Click Check Connection, it will return 200: OK
For more details, please read: Create Transport Destinations
The same as above.
For example:
In Cloud Transport Management, transport nodes represent source and target end points of a deployment process - for example, a Cloud Foundry subaccount. Transports take place between transport nodes.
Make sure you have one of the roles Administrator or LandscapeOperator assigned to your user.
You have the following options to create transport nodes:
In this post, we create node with option Transport Nodes.
Open the Transport Management home screen:
Navigate to Transport Nodes, click button + (Create a new node):
Fill in with the following information:
Since we need to manually upload MTA into the TEST_Node, select the Allow Upload to Node checkbox.
We need to set the Destination so as to deploy the application into corresponding space.
Click OK.
For more details, please read: Create Transport Nodes
Create a new one and fill in with the following information:
We need to set the Destination so as to deploy the application into corresponding space.
You can use the same transport node as a source node for multiple transport routes. However, you can use the same transport node only once as a target node for a transport route.
You have the following options to create transport nodes:
In this post, we create node with option Transport Routes.
On your SAP Cloud Transport Management home screen, click button + (Create a route):
Fill in with the following information:
Click OK.
For more details, please read: Create Transport Routes
In Cloud Transport Management, you upload a content archive to an import queue using the Add function. The upload process will create a transport request and attach the content archive to it, so that it will be available in the import queue of the TEST node for import (deploy) into the TEST subaccount. After being imported in the TEST subaccount, it is available in the import queue of the PROD_Node for import (deploy).
Go into the TEST_Node:
Click Add to upload the content archive into the import queue:
Choose the content archive:
Click OK.
Two actions were executed:
Select it and click Import Selected, the content archive will be imported (deployed) into TEST Subaccount and immediately transported into the PROD_Node:
Two actions were executed, which means the application has been successfully deployed into the TEST Subaccount and the content archive has been transported to the import queue of the PROD_Node:
Check the deployed application in the space of the TEST Subaccount:
Access it in the browser:
Now you can see the transport request in the import queue of the PROD_Node:
In the PROD_Node, select the transport request and click Import Selected, the content archive will be imported (deployed) into PROD Subaccount.
Check the deployed application in the space of the PROD Subaccount:
Now the whole transportation process has been finished.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
27 | |
24 | |
23 | |
19 | |
15 | |
15 | |
10 | |
8 | |
8 | |
8 |