- SAP Managed Tags:
This document provides an overview of the required steps you need to follow in order to enable the Promote feature in your SAP Build platform.
When the instance is created, create a service key. We will refer to this key as TMS key.
About the access rights : you need to assign the proper role collections (see documentation) to the users who will be in charge of allowing the transport of packages, through the Cloud Transport Management Service.
The following should be executed on both DEV and PROD subaccounts :
At this point, on each subaccount (DEV and PROD) you should have a destination targeting the Cloud Transport Management Service.
On the TMS subaccount, for each subaccount you need to link to TMS, create a destination having the following options:
At this point, you should have one destination targeting the Content Agent Service on DEV tenant, and another one targeting the Content Agent Service on PROD tenant.
Navigate to the Cloud Transport Management Service : from the TMS subaccount, open the Instances and Subscriptions menu, and click the link for the application Cloud Transport Management.
Open the Landscape Visualization menu. On the canvas, create a new Node, having the following options:
Note:
Create another Node for the SBPA PROD subaccount.
Once the 2 nodes are created, create a route between them. See below for the result :
At this point, your whole system is set up so you can use the Promote feature. On the Dev tenant, you'll be able to promote a released version of a package. Then you will have to make it available on your PROD tenant (using TMS application). There, you will be given the possibility to import the package.
Pre-requisites
- Make sure you have a dedicated subaccount for the DEV tenant of SAP Build Process Automation
- Make sure you have a dedicated subaccount for the PROD tenant of SAP Build Process Automation
Enable the Cloud Transport Management service
- In BTP Cockpit, create a new subaccount that will be dedicated to the transport of packages
- In this newly created subaccount, create an instance of the Cloud Transport Management service, using the standard plan
When the instance is created, create a service key. We will refer to this key as TMS key.
About the access rights : you need to assign the proper role collections (see documentation) to the users who will be in charge of allowing the transport of packages, through the Cloud Transport Management Service.
Enable the Content Agent Service application
- On the DEV subaccount, navigate to the Service Marketplace and create an instance of the service Content Agent Service, using the application plan
- Assign all the roles
- Once the instance is created, create a service key. We will refer to this key as Dev Content key
- Repeat the procedure for the PROD subaccount. We will refer to the service key on PROD subaccount as PROD Content key.
Create the link from SBPA subaccount to the Cloud Transport Management service
The following should be executed on both DEV and PROD subaccounts :
- Create a destination with the following options:
| Name | TransportManagementService (do not change the name of the destination) |
| Type | HTTP |
| URL | URL of the TMS key |
| Proxy Type | Internet |
| Authentication | OAuth2ClientCredentials |
| Client ID | ClientId of the TMS key |
| Client Secret | ClientSecret of the TMS key |
| Token Service URL Type | Dedicated |
| Token Service URL | Authentication URL of the TMS key. Append /oauth/token at the end of this URL |
- Create an additional property sourceSystemId with the name of the tenant. Ex: StoreContent_DEV
At this point, on each subaccount (DEV and PROD) you should have a destination targeting the Cloud Transport Management Service.
Create the link from Cloud Transport Management Service to SBPA subaccount
On the TMS subaccount, for each subaccount you need to link to TMS, create a destination having the following options:
| Name | Name of the destination. It will be used later in the configuration of TMS Ex: ContentAgent_DEV |
| Type | HTTP |
| URL | URL of the Content key |
| Proxy Type | Internet |
| Authentication | OAuth2ClientCredentials |
| Client ID | ClientId of the Content key |
| Client Secret | ClientSecret of the Content key |
| Token Service URL Type | Dedicated |
| Token Service URL | Authentication URL of the Content key. Append /oauth/token at the end of this URL |
At this point, you should have one destination targeting the Content Agent Service on DEV tenant, and another one targeting the Content Agent Service on PROD tenant.
Configure the Cloud Transport Management Service
Navigate to the Cloud Transport Management Service : from the TMS subaccount, open the Instances and Subscriptions menu, and click the link for the application Cloud Transport Management.
Open the Landscape Visualization menu. On the canvas, create a new Node, having the following options:
Note:
- the name of the node should be the value you set for the additional property sourceSystemId for the destination on the SBPA DEV subaccount.
- the destination should be the one corresponding to the SBPA DEV tenant on the TMS subaccount
Create another Node for the SBPA PROD subaccount.
Once the 2 nodes are created, create a route between them. See below for the result :
Conclusion
At this point, your whole system is set up so you can use the Promote feature. On the Dev tenant, you'll be able to promote a released version of a package. Then you will have to make it available on your PROD tenant (using TMS application). There, you will be given the possibility to import the package.
4 Comments
