SAP Cloud Platform Transport Management: User Guide - Public Document Version: 1.0 - 2020-06-08

USER GUIDE | PUBLIC
Document Version: 1.0 – 2020-06-08
SAP Cloud Platform Transport Management

© 2020 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 What is SAP Cloud Platform Transport Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 What's New for Transport Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.1 2019 Transport Management (Archive). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 2018 Transport Management (Archive). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3 Initial Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1 Provide Access to SAP Cloud Platform Transport Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2 Set Up the Environment to Transport Content Archives directly in an Application. . . . . . . . . . . . . . . .15
3.3 Set Up the Environment to Transport Content Archives that are available on a Local File System
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
4 SAP Cloud Platform Transport Management Home Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . .24
5 Configuring the Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

5.1 SAP Cloud Platform Transport Management Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Sample Configuration Scenario: Transport of Content Archives directly in another Application
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Sample Configuration Scenario: Transport of Content Archives that are available on Local File
Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.2 Create Transport Destinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.3 Create Transport Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.4 Create Transport Routes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.5 Use the Transport Landscape Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.6 Create Destinations to SAP Cloud Platform Transport Management. . . . . . . . . . . . . . . . . . . . . . . . 39
6 Using the Landscape Visualization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
7 Using the Import Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

7.1 Add Files to Import Queues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
7.2 Import Transport Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
7.3 Schedule Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7.4 Upload MTA Extension Descriptors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
8 Landscape Action Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
9 Transport Action Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
10 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
11 Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

2 PUBLIC Content
12 Receive Notifications for Import Actions Using SAP Cloud Platform Alert Notification. . . . . . 60
13 Data Protection in SAP Cloud Platform Transport Management. . . . . . . . . . . . . . . . . . . . . . . . 63
14 Monitoring and Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Content PUBLIC 3
1 What is SAP Cloud Platform Transport
Management
SAP Cloud Platform Transport Management manages application transport and content transport within a
landscape on SAP Cloud Platform.
SAP Cloud Platform Transport Management runs in Cloud Foundry Environment and can be used to transport
the following entities:
● Multitarget Application archives (MTAs -.mtar files) between different cloud subaccounts
MTAs can consist of a cloud application itself, or content created in a cloud application, which you want to
transport between two subaccounts.
● Delivery units (DUs) of SAP HANA XS classic model between different SAP HANA instances that are
assigned to cloud subaccounts
● Application content transported in an application-specific format between different cloud subaccounts
The .zip files can contain any kind of application-specific content. The application that has created
these .zip files must provide a deploy method to deploy the application content on the target subaccount.
For more information, see the documentation of the individual applications.
The files can be transported in one of the following scenarios:
● Directly from within another application

● They are available on local file systems
For more information, see SAP Cloud Platform Transport Management Scenarios [page 29].
SAP Cloud Platform Transport Management runs in Cloud Foundry as a multi-tenant aware application and
supports a tenant separation.
It offers user interfaces that can be used in the following ways:
● Using a graphical user interface

To use this, you need a subscription to SAP Cloud Platform Transport Management in your subaccount.
● Using programmatic access (API remote call)
To use this, you need a service instance that is used to call the export functionality of SAP Cloud Platform
Transport Management. You must create this service instance in a space of the subaccount from which you
have subscribed to SAP Cloud Platform Transport Management.
For more information, see Initial Setup [page 14].
Features
● Software-as-a-Service (SaaS) solution in Cloud Foundry with tenant separation

● Flexible tool to transport various types of content - MTAs, XS classic DUs, application-specific content
(.zip files)
● Setup of complex landscapes possible
● No ABAP on-premise system required, completely cloud-based

4 PUBLIC What is SAP Cloud Platform Transport Management
● No additional infrastructure or third-party services required
More Information
● Multitarget Applications in the Cloud Foundry Environment

● Multitarget Applications for the Neo Environment

What is SAP Cloud Platform Transport Management PUBLIC 5
2 What's New for Transport Management
2020
Techni
cal Envi Availa
Com Capa ron ble as
ponent bility ment Title Description Type of
Trans Exten Cloud SAP Transport Management now allows you to customize the MTA de Chang 2020-0
ployment for specific transport nodes in Cloud Foundry environ
port sion Foun Cloud ed 6-08
ment using MTA extension descriptors. See Upload MTA Exten
Man Suite - dry Plat
sion Descriptors [page 50].
age Devel form
ment opment Trans
Effi- port
ciency Man
age
ment
Service
Trans Exten Cloud SAP Transport Management now delivers attributes for the role tem Chang 2020-0
plates TransportOperator, ExportOperator, and ImportOperator.
port sion Foun Cloud ed 5-22
You can use the attributes to restrict the authorizations of a role to
specific transport nodes only. See Security [page 56].
age Devel form
ment opment Trans
Effi- port
ciency Man
age
ment
Service
Trans Exten Cloud SAP ● Transport Management is now also available on Amazon Web Chang 2020-0
port sion Foun Cloud Services in the Singapore, Brazil (São Paulo), and Japan (To ed 5-08
kyo) areas, and on Microsoft Azure in the Europe (Nether
lands), Japan (Tokyo), Singapore, US West (WA), and US East
age Devel form
(VA) areas. See SAP Cloud Platform Regions and Service
ment opment Trans Portfolio.
Effi- port ● SAP Cloud Transport Management integration in CI/CD pipe
ciency Man lines available using Project "Piper". See also:
age ○ Documentation of the scenario in Project "Piper": Inte
ment grate SAP Cloud Platform Transport Management Into
Service Your CI/CD Pipeline
○ Blog: How to integrate SAP Cloud Platform Transport
Management into your CI/CD pipeline
● New blog: How to use the integration of SAP Cloud Platform
Transport Management into SAP Solution Manager Change
Request Management and Quality Gate Management .

6 PUBLIC What's New for Transport Management
Techni
cal Envi Availa
Com Capa ron ble as
Trans Exten Cloud SAP ● Import scheduler has been enhanced to make scheduling Chang 2020-0
port sion Foun Cloud more flexible. See Schedule Imports [page 49]. ed 3-19
Man Suite - dry Plat ● New introductory mission about SAP Cloud Platform Trans
port Management now available in SAP Cloud Platform Dis
age Devel form
covery Center. See Setup SAP Cloud Platform Transport
ment opment Trans
management to move content between subaccounts .
Effi- port
ciency Man
age
ment
Service
Trans Exten Cloud SAP ● SAP Cloud Platform Alert Notification service is now inte Chang 2020-0
port sion Foun Cloud grated in SAP Cloud Platform Transport Management. You ed 1-29
can configure to receive notifications about when imports are
started and finished. See also: Receive Notifications for Im
age Devel form
port Actions Using SAP Cloud Platform Alert Notification
ment opment Trans [page 60]
Effi- port ● The selection of pages was changed in Transport Action Logs
ciency Man and Landscape Action Logs.
age ● SAP Cloud Platform Transport Management now supports
ment more than one entry route for any node.
Service
For all Release Notes from 2019, see 2019 Transport Management
(Archive) [page 7].
2.1 2019 Transport Management (Archive)

What's New for Transport Management PUBLIC 7
2019
Techni
cal Envi Availa
Com Capa ron ble as
Trans Plat Cloud SAP ● SAP Cloud Transport Management now also available on Am Chang 2019-1
port form Foun Cloud azon Web Services in the Canada (Montreal) region. See SAP ed 2-19
Cloud Platform Regions and Service Portfolio.
Man Foun dry Plat
● All times displayed in SAP Cloud Transport Management are
age dation form
now displayed in local time.
ment Trans
● The layout of SAP Cloud Transport Management has been
port
switched to the SAP Quartz theme.
Man ● Improvements have been made for parallel file upload. You
age can now monitor the progress of a file upload process of
ment larger files. See also: SAP Cloud Platform Transport Manage
Service ment Home Screen [page 24]
Trans Plat Cloud SAP ● New blog available about How to set up SAP Transport Man Chang 2019-11
port form Foun Cloud agement service for SAP Cloud Platform Integration ed -21
Man Foun dry Plat ● The BC-NEO-LCM-TMS component to report incidents has
been renamed to BC-CP-LCM-TMS.
age dation form
● Capabilities were changed. SAP Cloud Platform Transport
ment Trans
Management Service is now assigned to the Platform Founda
port
tion capability.
Man
age
ment
Service
Trans Plat Cloud SAP ● Improved handling of user session time out Chang 2019-11
port form Foun Cloud ● Improved stability for file upload ed -12
Man Foun dry Plat
age dation form
ment Trans
port
Man
age
ment
Service
Trans Plat Cloud SAP ● SAP Cloud Platform Transport Management is now available Chang 2019-1
port form Foun Cloud in SAP Cloud Platform Trial. See the blog SAP Cloud Platform ed 0-28
Transport Management service now available in trial environ
Man Foun dry Plat
ment .
age dation form
● Monitoring and Troubleshooting [page 65] topic was added
ment Trans
to SAP Cloud Platform Transport Management documenta
port tion.
Man
age
ment
Service

Techni
cal Envi Availa
Com Capa ron ble as
Trans Plat Cloud SAP ● SAP Cloud Transport Management now shows the number of Chang 2019-0
port form Foun Cloud transport request in status Initial/Repeatable, Running, ed 9-12
Man Foun dry Plat Succeeded, Warning, Error and Fatal per node.
age dation form ● An additional node property to put a node under the control
ment Trans of Change Request Management was introduced.
port
Man
age
ment
Service
Trans Plat Cloud SAP ● SAP Cloud Transport Management now also available on Am Chang 2019-0
port form Foun Cloud azon Web Services in the Australia (Sydney) region. See SAP ed 8-21
Cloud Platform Regions and Service Portfolio.
Man Foun dry Plat
● In the import queue of a transport node, you can now select
age dation form
individual or multiple queue entries for actions, such as
ment Trans
Forward, Reset, and Remove the selected queue entries.
port
● A new Warning status for transports was introduced.
Man ● Import actions in the Running status are now refreshed at
age regular intervals when you are in the import queue of the
ment transport node.
Service ● Documentation contains a new section about the audit logs
written by SAP Cloud Transport Management. See Security
[page 56].
Trans Plat Cloud SAP The import queue of a transport node now displays information New 2019-0
about scheduled imports in the header part, if imports are sched
port form Foun Cloud 7-23
uled. See Using the Import Queue [page 44].
Man Foun dry Plat
age dation form
ment Trans
port
Man
age
ment
Service

Techni
cal Envi Availa
Com Capa ron ble as
Trans Plat Cloud SAP Landscape Visualization now available. Use the visual display to New 2019-0
configure, edit, or view your your transport landscape, as well as
get an overview of the status of your imports. See Using the Land
Man Foun dry Plat
scape Visualization [page 41].
age dation form
ment Trans
port
Man
age
ment
Service
Trans Plat Cloud SAP SAP Cloud Transport Management Export API now available on New 2019-0
SAP API Hub . See Integration [page 59].
Man Foun dry Plat
age dation form
ment Trans
port
Man
age
ment
Service
Trans Plat Cloud SAP In the import queue of a transport node, the owner of the trans Chang 2019-0
port request is now displayed in a separate column.
port form Foun Cloud ed 6-21
Man Foun dry Plat See Using the Import Queue [page 44].
age dation form
ment Trans
port
Man
age
ment
Service
Trans Plat Cloud SAP In the import queue of a transport node, the following information Chang 2019-0
is now displayed:
port form Foun Cloud ed 5-10
Man Foun dry Plat ● Node in which a transport request was initially added to the
queue (in the Entry Node column)
age dation form
● For .mta files, you can now display the content of the multi
ment Trans
port target application (using the  (See this transport request's
content metadata) icon).
Man
age See Using the Import Queue [page 44].
ment
Service

Techni
cal Envi Availa
Com Capa ron ble as
Trans Plat Cloud SAP In-app help is now available. To enable it, choose the  icon in the Chang 2019-0
port form Foun Cloud header bar. See SAP Cloud Platform Transport Management ed 4-29
Man Foun dry Plat Home Screen [page 24].
age dation form
ment Trans
port
Man
age
ment
Service
Trans Plat Cloud SAP SAP Cloud Platform Transport Management Service is now also Chang 2019-0
port form Foun Cloud available for subscription-based customers via SAP Store. See ed 4-29
Man Foun dry Plat SAP Cloud Platform Transport Management in SAP Store .
age dation form
ment Trans
port
Man
age
ment
Service
Trans Plat Cloud SAP You can now import individual transport requests. See Import Chang 2019-0
port form Foun Cloud Transport Requests [page 47]. ed 3-29
Man Foun dry Plat
age dation form
ment Trans
port
Man
age
ment
Service

Techni
cal Envi Availa
Com Capa ron ble as
Trans Plat Cloud SAP ● New function Import Scheduler added: In the Import queue of Chang 2019-0
port form Foun Cloud a transport node, you can schedule imports of all transports ed 3-01
to run at a specified time (for example, hourly, daily, and so
Man Foun dry Plat
on).
age dation form
For more information, see Using the Import Queue [page 44].
ment Trans
● You can now influence the forwarding mode of transport re
port
quests in a transport node: You can configure whether or not
Man transports in the node are automatically forwarded to the im
age port queues of the target nodes when an import is started. If
ment you set the Forward Mode to Automatic, they are automati
Service cally forwarded. You can also set the Forward Mode to Manual,
and decide which ones to forward manually later.
For more information, see Create Transport Nodes [page 35].
● In the Transport Action Logs view, you can now download all
transport action logs to one archive file.
For more information, see Transport Action Logs [page 54].
● Transport Management is now also available on Amazon Web
Services in the US East (VA) region.
Trans Plat Cloud SAP ● When you create or change a transport node, both using the Chang 2019-0
port form Foun Cloud Transport Landscape Wizard and the Transport Nodes view, ed 1-31
you can now directly navigate to the Destination view of your
Man Foun dry Plat
subaccount in SAP Cloud Platform Cockpit.
age dation form
● Bug fixes and UI improvements
ment Trans
port
Man
age
ment
Service
2.2 2018 Transport Management (Archive)

2018
Techni
cal Envi Availa
Com Capa ron ble as
Trans DevOps Cloud SAP General Availability of Transport Management Service New 2018-11
port Foun Cloud -22
For more information, see SAP Cloud Platform Transport Manage
Man dry Plat
ment [page 4].
age form
ment Trans
port
Man
age
ment
Service

3 Initial Setup
To use SAP Cloud Platform Transport Management, a cloud administrator needs to provide access to it, and set
up the environment.
You should decide beforehand whether you will use SAP Cloud Platform Transport Management to transport
content archives that are available on local file systems, or to transport content archives directly in another
application. Depending on the scenario, different configuration steps are involved. For more information on the
scenarios, see SAP Cloud Platform Transport Management Scenarios [page 29].
To get started with SAP Cloud Platform Transport Management, cloud administrators perform the following
steps:
1. Provide Access to SAP Cloud Platform Transport Management [page 14]
Provide access to SAP Cloud Platform Transport Management.
2. Set Up the Environment to Transport Content Archives directly in an Application [page 15]
Set up your cloud environment to use SAP Cloud Platform Transport Management to transport content archives
directly in another application, SAP Cloud Platform Integration, for example. You need to perform the steps that
are required to use the user interface of SAP Cloud Platform Transport Management , and to use it using pro
grammatic access (API remote call).
Set Up the Environment to Transport Content Archives that are available on a Local File System [page 20]
Set up your cloud environment to use SAP Cloud Platform Transport Management to transport content archives
that are available on local file systems. You need to perform the steps that are required to use the user interface
of SAP Cloud Platform Transport Management.
3. Configuring the Landscape [page 28]
Model your transport landscape. To do this, configure destinations in Cloud Foundry Environment Cockpit, and
transport nodes and transport routes in SAP Cloud Platform Transport Management.
3.1 Provide Access to SAP Cloud Platform Transport

Management
SAP Cloud Platform Transport Management is offered both using the Consumption-Based and the
Subscription-based Commercial Model. For more information, see Commercial Models in the SAP Cloud
Platform Planning and Lifecycle-Management guide.
To provide access to SAP Cloud Platform Transport Management, as a global account administrator, assign a
service entitlement for the transport reuse service to the subaccounts where SAP Cloud Platform Transport
Management will be used.
For more information, see Configure Entitlements and Quotas for Subaccounts.

14 PUBLIC Initial Setup
Next Steps:
Set Up the Environment to Transport Content Archives directly in an Application [page 15]
Set Up the Environment to Transport Content Archives that are available on a Local File System [page 20]
3.2 Set Up the Environment to Transport Content Archives

directly in an Application
Before you can transport content archives directly in an application, the cloud administrator needs to set up
the environment for this.
 Note
Most of the steps described below can be done either using Cloud Foundry Environment Cockpit or Cloud
Foundry command line interface.
The following tables describe the steps in Cloud Foundry Environment Cockpit. For each step, they contain
links to general documentation about the actions. There, you will also find information about how to
perform the steps using the Cloud Foundry command line interface.
Steps to use the User Interface of Transport Management
Step Action Video More Information
1. In your global account, choose an existing Cloud Create a Subaccount

Foundry subaccount in which you want to use [Feature Set A]
Open this video in a new window
Transport Management, or create a new Cloud
Foundry subaccount.
2. Enable Cloud Foundry to create an organization Create Spaces

in the subaccount.
1. Choose Enable Cloud Foundry.
2. Choose a name for your organization and
choose Create.

Initial Setup PUBLIC 15
3. Subscribe to the Transport Management appli Getting Started with

cation. Multitenant Applica
tion Subscriptions in
1. In the subaccount, choose Subscriptions.
the Cloud Foundry En
The entitled subscriptions are shown.
vironment
2. Select the Transport Management tile, and
choose Subscribe.
The subscription is activated. The Go to

Application link is available that allows you to
start the user interface of Transport
Management.

Steps to Assign User Roles and Permissions
4. After successful subscription, you need to cre Create role collections: Maintain Role Collec
ate different role collections for the different tions
Transport Management roles, and assign roles
to the role collections. Open this video in a new window
1. In your subaccount, choose Security Assign roles to role collections:
Role Collections New Role Collections .

2. Enter a name for the new role collection,
and choose Save.
3. Choose Subscriptions, and, in the Transport
Management - Subscribed tile, choose the
Transport Management link.
4. On the subscription overview screen,
choose Manage Roles.
All roles that are available for SAP Cloud

Platform Transport Management are dis
played.
5. Select the role that you want to add to the
role collection created before, and choose
 (Add to a Role Collection).
6. Select the role created before, and choose
Save.
7. Repeat the previous steps if you need to
create different role collections for different
tasks.
For example, you can create a role collec
tion for administration tasks that contains
the Administrator role, and a role collection
for developers with ExportOperator role.
For more information on the available roles,
see Security [page 56].
5. After you have created the role collections, as Assign Role Collec
sign them to users or user groups. tions

Steps to use Transport Management using Programmatic Access (API
Remote Call)
6. Assign an entitlement to Transport Configure Entitlements

Management for your subaccount. and Quotas for Subac
1. Go to your global account. counts
2. Choose Entitlements Subaccount

Assignments .
3. Select your subaccount from the dropdown
list, and choose Go.
4. Choose Configure Entitlements, and then
Add Service Plans.
5. From the Service Catalog, select Transport
Management, and, under Available Service
Plans, select the standard checkbox.
Choose Add 1 Service Plan.
6. To save the service plan, choose Save.
The service plan for Transport Management is

now assigned to your subaccount.
7. In the Cloud Foundry organization, create a Create Spaces

space.
1. Go to your subaccount.
2. Choose Spaces.
3. Choose New Space.
4. Choose a name and leave the default space
roles unchanged.

8. Create a quota plan for your space. A quota plan Assign Quota Plans to
with at least one service is required. Spaces
1. Go to your subaccount, and choose
Quota Plans New Plan .
2. Enter a name, and 1 service, and choose
Save.
3. To assign the quota plan to your space, un

der Plan Assignment, choose the quota
plan from the dropdown list of the created
space.
9. In the space, create a service instance of Creating Service In

Transport Management. stances
1. In the space, choose Services .
2. From the Service Marketplace, choose the
Transport Management tile.
3. Choose Instances New Instance .

4. In the Create Instance wizard, you can
choose Next until you are asked to enter a
name for the instance.
5. Enter an instance name and choose Finish.

10. Create a service key based on the service in Creating Service Keys
stance for Transport Management.
1. In the service instance, choose Service
Keys Create Service Key .
2. Enter a name for the service key, and
choose Save.
The connection details are used later to config-

ure destinations in your cloud subaccount to
Transport Management.
For more information about how to configure

the destinations, see Create Destinations to
[page 39].
You can now open the user interface of Transport Management. To do this, go to your subaccount, and choose
Subscriptions. In the Transport Management Service tile, choose Go to Application. Log on with your e-mail
address and password as usual.
You can now configure the landscape and use Transport Management directly in other applications, such as
SAP Cloud Platform Integration.
Next steps:
Configuring the Landscape [page 28]
3.3 Set Up the Environment to Transport Content Archives

that are available on a Local File System
Before you can transport content archives that are available on a local file system, the cloud administrator
needs to set up the environment for this.
 Note
Most of the steps described below can be done either using Cloud Foundry Environment Cockpit or Cloud
Foundry command line interface.
The following tables describe the steps in Cloud Foundry Environment Cockpit. For each step, they contain
links to general documentation about the actions. There, you will also find information about how to
perform the steps using the Cloud Foundry command line interface.

Steps to use the User Interface of Transport Management
1. In your global account, choose an existing Cloud Create a Subaccount

Foundry subaccount in which you want to use [Feature Set A]
Transport Management, or create a new Cloud
Foundry subaccount.
2. Subscribe to the Transport Management appli Getting Started with

cation. Multitenant Applica
tion Subscriptions in
1. In the subaccount, choose Subscriptions.
the Cloud Foundry En
The entitled subscriptions are shown.
vironment
2. Select the Transport Management tile, and
choose Subscribe.
The subscription is activated. The Go to

Application link is available that allows you to
start the user interface of SAP Cloud Platform

Steps to Assign User Roles and Permissions
3. After successful subscription, you need to cre Create role collections: Maintain Role Collec
ate different role collections for the different tions
Transport Management roles, and assign the
roles to role collections. Open this video in a new window
1. In your subaccount, choose Security Assign roles to role collections:
Role Collections New Role Collections .

2. Enter a name for the new role collection,
and choose Save.
3. Choose Subscriptions, and, in the Transport
Management - Subscribed tile, choose the
Transport Management link.
4. On the subscription overview screen,
choose Manage Roles.
All roles that are available for SAP Cloud

Platform Transport Management are dis
played.
5. Select the role that you want to add to the
role collection created before, and choose
 (Add to a Role Collection).
6. Select the role created before, and choose
Save.
7. Repeat the previous steps if you need to
create different role collections for different
tasks.
For example, you can create a role collec
tion for administration tasks that contains
the Administrator role, and a role collection
for developers with ExportOperator role.
For more information on the available roles,
4. After you have created the role collections, as Assign Role Collec
sign them to users or user groups. tions

You can now open the user interface of SAP Cloud Platform Transport Management. To do this, go to your
subaccount, and choose Subscriptions. In the Transport Management Service tile, choose Go to Application.
Log on with your e-mail address and password as usual.
You can now configure the landscape and use SAP Cloud Platform Transport Management to transport content
archives that are available on a local file system.
Next steps:
Configuring the Landscape [page 28]

4 SAP Cloud Platform Transport
Management Home Screen
On the home screen, you have an overview of the most commonly used functions of SAP Cloud Platform
Transport Management with direct access. Using the navigation pane on the left side, you have access to all
functions.
● #unique_11/unique_11_Connect_42_subsection-im1 [page 25]

Hover over each element for a description. Click the element for more information.
Navigation Pane
Use the navigation pane to access all functions available in SAP Cloud Platform Transport Management, such
as configuring the landscape, executing, or monitoring transports.

24 PUBLIC SAP Cloud Platform Transport Management Home Screen
Transport Management
On the Transport Management section on the home screen, you can monitor imports and get an overview of
transports.
Monitor Imports
The pie chart gives an overview of the imports. You can select the time interval for which you want to display
the chart, and you can directly navigate to the Transport Action Logs.
Transports Waiting for Import

The list displays the transport nodes whose import queues have the highest number of queue entries, and
which contain transports waiting for import. This means, there are transports in the queue that are in status
initial, fatal, or repeatable. If you want to navigate to the import queue of a specific transport node, click
anywhere in the row.
To see all transport nodes, choose Show more. This will open the Transport Nodes overview.
For more information, see Create Transport Nodes [page 35].
Landscape Management
On the Landscape Management section on the home screen, you can navigate to the Landscape Wizard or to
the Landscape Wizard to configure your transport landscape.
Landscape Wizard
You can use the Landscape Wizard to easily configure simple transport landscapes. If you know the number of
transport nodes of which your landscape will consist, you can configure the landscape using a template.
For more information, see Use the Transport Landscape Wizard [page 38].
About
You can click on your logon e-mail address or the dropdown arrow on the top right to log out of SAP Cloud
Platform Transport Management or to get more information about the current version of SAP Cloud Platform
Transport Management, your file quota, log out of SAP Cloud Platform Transport Management.

SAP Cloud Platform Transport Management Home Screen PUBLIC 25
Application Messages
You can display all messages that SAP Cloud Platform Transport Management issues during your logon
session. To do this, click on the (Application Messages) button.
In-App Help
You can display in-app help by clicking on (In-App Help). An information bar appears on the right-hand
side of the screen, and text elements in the bar are linked with elements on the screen. To get help on a screen
element, click on the circle.
When in-app help is enabled, the question mark icon will change to .
Landscape Visualization
You can use the Landscape Visualization to easily configure transport landscapes in a visual display.
For more information, see Using the Landscape Visualization [page 41].

26 PUBLIC SAP Cloud Platform Transport Management Home Screen
Monitor progress of file upload process
To monitor the progress of a file upload process of larger files, in the import queue of a transport node, you can
choose (Progress details on your current file uploads). The progress of all file uploads of your user in the
current browser session is displayed.
For more information, see Add Files to Import Queues [page 46].

SAP Cloud Platform Transport Management Home Screen PUBLIC 27
5 Configuring the Landscape
Before you can use SAP Cloud Platform Transport Management to transport cloud applications or application
content (such as SAP Cloud Platform Integration content, for example) between different subaccounts, you
must configure your landscape for transports.
Depending on the scenario in which you want to use SAP Cloud Platform Transport Management, different
configuration tasks are required. The scenarios are:
● Transport of Content Archives directly in another Application

● Transport of Content Archives that are available on Local File Systems
For more information on the scenarios, see SAP Cloud Platform Transport Management Scenarios [page 29].
The configuration involves the following steps:
● Create Transport Destinations [page 32]

● Create Transport Nodes [page 35]

28 PUBLIC Configuring the Landscape
● Create Transport Routes [page 37]
● Create Destinations to SAP Cloud Platform Transport Management [page 39]
● Create Destinations to SAP Cloud Platform Transport Management [page 39]
SAP Cloud Platform Transport Management offers different options to perform the configuration steps:
● Using the Landscape Visualization [page 41]

● Using the Landscape Wizard [page 38]
● By manually configuring the individual entities:
○ Create Transport Destinations [page 32]
○ Create Transport Nodes [page 35]
○ Create Transport Routes [page 37]
5.1 SAP Cloud Platform Transport Management Scenarios
SAP Cloud Platform Transport Management is used in the following ways:
● Transport of Content Archives directly in another Application

In this scenario, another application whose content archives you want to transport, such as SAP Cloud
Platform Integration, is directly integrated with SAP Cloud Platform Transport Management. You can
transport content archives directly from within the application´s source subaccount to the target
subaccount of the application. You can then use SAP Cloud Platform Transport Management to import the
content archives in the target subaccount.
See also: Sample Configuration Scenario: Transport of Content Archives directly in another Application
[page 29]
● Transport of Content Archives that are available on Local File Systems
In this scenario, the content archives that you want to transport between different subaccounts, are
downloaded in the application of the source subaccount. They are then available on your local file system.
You can use SAP Cloud Platform Transport Management to upload the content archives to the import
queue of the target subaccount and import them in the target subaccount.
See also: Sample Configuration Scenario: Transport of Content Archives that are available on Local File
Systems [page 31]
5.1.1 Sample Configuration Scenario: Transport of Content

Archives directly in another Application
The following sample configuration describes the scenario: Transport of content archives directly in another
application.
The content archives will be attached to transport requests directly in the application and will be transported
along the configured transport routes.

Configuring the Landscape PUBLIC 29
Sample Configuration for Scenario: Transport of Content Archives directly in another Application
You have a cloud application, such as SAP Cloud Platform Integration. You have different subaccounts, for
example, a DEV subaccount, a TEST subaccount, and a PROD subaccount where your application runs. You
want to transport content archives (.mtar files, for example) of this application from one subaccount to
another. To perform the transport directly in the application, the following entities must be configured:
Entities to be configured Where to configure? More information
Transport destinations of the In your SAP Cloud Platform Cockpit Cloud Foundry en Create Transport Destinations
TEST and PROD subaccounts vironment subaccount [page 32]
Transport nodes for the DEV, Using the Transport Landscape Wizard in the SAP Use the Transport Landscape
TEST, and PROD subaccounts, Cloud Platform Transport Management Wizard [page 38]
and transport routes between
the nodes
A destination from the DEV In the DEV subaccount of the application Create Destinations to SAP
subaccount pointing to the SAP Cloud Platform Transport Man
Cloud Platform Transport agement [page 39]
Management
If you select a content archive for direct transport, this will create a transport request in the DEV node, attach
the content archive to the transport request, and place it in the import queue of the TEST node. The content
archive will be available in the import queue of the TEST node for import in the TEST subaccount. After being
imported in the TEST subaccount, it is available for import in the PROD subaccount.
 Note
For more information about the transport of SAP Cloud Platform Integration content directly in the
application, see Content Transport Using Transport Management Service in the SAP Cloud Platform
documentation.

5.1.2 Sample Configuration Scenario: Transport of Content
Archives that are available on Local File Systems
The following sample configuration describes the scenario: Transport of Content Archives that are available on
Local File Systems.
The content archive has been downloaded or exported from an application in the source DEV subaccount to a
local file system. It is then added to the import queue of the TEST node in SAP Cloud Platform Transport
Management so that it can be imported to the TEST subaccount.
Sample Configuration for Scenario: Transport of Content Archives that are available on Local File Systems
You have a cloud application, such as SAP Cloud Platform Integration. For this application, you have different
subaccounts, for example, a DEV subaccount, a TEST subaccount, and a PROD subaccount. You create a
content archive (.mtar files, for example) in the DEV subaccount of the application and you want to transport
it to the TEST and PROD subaccounts. You can choose to perform the transport not directly in the application,
but to download or export the content archive in the application of the DEV subaccount to your local file
system.
To transport the content archive that is available on the local file system, the following entities must be
configured:
Entities to be configured Where to configure? More information
Transport destinations to the In your SAP Cloud Platform Cockpit Cloud Foundry en Create Transport Destinations
TEST and PROD subaccounts vironment subaccount [page 32]
Transport nodes for the TEST Using the Transport Landscape Wizard in the SAP Use the Transport Landscape
and PROD subaccounts, and a Cloud Platform Transport Management Wizard [page 38]
transport route between the no
des
In SAP Cloud Platform Transport Management, in the import queue of the TEST node, 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 in the
TEST subaccount. After being imported in the TEST subaccount, it is available for import in the PROD
subaccount.

 Note
For more information about the transport of SAP Cloud Platform Integration content using download, see
Content Transport using MTAR Download in the SAP Cloud Platform Integration documentation.
5.2 Create Transport Destinations
In SAP Cloud Platform Transport Management, transport destinations are used to address the target end point
of a deployment process.
Context
Destinations contain the address of the target end point as well as the user credentials.
You create a destination in Cloud Foundry Environment Cockpit of your subaccount, and not within SAP Cloud
Platform Transport Management.
 Note
For general information about how to configure destinations, see Configure Destinations from the Cockpit.
Although this documentation describes the process for the Neo environment, it is also valid for Cloud
Foundry environment
Procedure
1. In Cloud Foundry Environment Cockpit of your subaccount, choose Connectivity Destinations New
Destination .
2. Enter the following details:
Description
Name Name of the destination
Type Choose HTTP.
Description (optional) You can enter a description for the destination.
URL Specify the URL to the deploy end point of the destination.

Description
○ In case of MTA deployment on Neo, the deploy end point is the Solutions Lifecycle Man
agement service: https://<host>/slservice/slp/basic/<ID of the
Neo account>/slp.
Example: https://slservice.eu1.hana.ondemand.com/
slservice/slp/basic/a123c4567b/slp
For more information, see Configuring the Access to the Solutions Lifecycle Management
Service.
○ In case of MTA deployment on Cloud Foundry, the deploy end point is the Deploy Service:
https://deploy-service.cfapps.<default-domain>/slprot/
<myorg>/<myspace>/slp.
Example: https://deploy-service.cfapps.eu10.hana.ondemand.com/
slprot/myorg/myspace/slp
As a result, the MTA will be deployed into the space myspace of the organization myorg.
The deploy service is available on the default domain of the subaccount. Usually, the de
fault domain is the first shared domain that is listed by the command cf domains of
the Cloud Foundry Command Line Interface (CLI). If multiple shared domains are listed,
validate the URL by issuing a GET request for the listed shared domains. The response for
the correct (default) domain is 200.
Example:
Request: GET https://deploy-
service.cfapps.eu10.hana.ondemand.com/public/ping
Response: 200 OK.
○ In case of XSC DU deployment, the URL is: https://<host>/sap/
hana/xs/lm/slp/slp.xsjs
Example: https://demoa71c4e71b.hana.ondemand.com/sap/
hana/xs/lm/slp/slp.xsjs
○ In case of application content transported in an application-specific format, the applica
tion specifies a URL to the deploy end point of the destination as well as the other details
of the destination.
○ In case of MTA deployment on Neo, select BasicAuthentication.

Authentication
○ In case of MTA deployment on Cloud Foundry, select BasicAuthentication. You have the
following options:
○ Classic Basic Authentication
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.
○ Basic Authentication with OAuth2-based Authentication
This authentication is based on a user credential flow. A 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. At first, the Cloud Foundry User Account
and Authentication (UAA) service is called with the name and the password of this
user. The authentication service then returns a JSON Web Token (JWT) which is used
to call the API of the Deploy Service. Please note that if you want to use the Oauth2-
based authentication, the destination must have an additional property, called
USER_TOKEN_URL, pointing to the Cloud Foundry UAA authentication service, for
example https://login.cf.sap.hana.ondemand.com.

Description
○ In case of application content transported in an application-specific format, use

OAuth2ClientCredentials authentication with a client credential flow. Here, you have to
configure a destination with authentication OAuth2ClientCredentials where the
client_id and the client_secret are needed that you get from the application or
service instance created in the target tenant. In addition, you have to specify the token
serviced url, pointing to the authentication service used, for example https://
ts.authentication.sap.hana.ondemand.com, which is also provided by the
application or service instance created in the target tenant.
User When using Basic Authentication: Specify the name of the technical user that is used for the
deployment.
For OAuth2-based authentication, enter the client_id.
Note that the user used for the destination is not subject to any Data Protection and Privacy
requirements.
Password When using Basic Authentication: Specify the password of the technical user.
For OAuth2-based authentication, enter the client_secret.
Use default JDK This checkbox is selected by default.

truststore
If you leave the checkbox selected, the default JDK truststore with certificates provided by
SAP are used.
If you want to change this, see Use Destination Certificates (Cockpit).
3. Choose Save to save your changes.

4. Optional: Test the destination that you just created.
To do this, choose  (Check availability of destination connection) for the destination.
Note that in case of MTA deployment on Cloud Foundry and in case of application content transported in
an application-specific format, the connection test may give the wrong response (Connection not ok) even
though the destination was correctly configured.
Results
The destination was created. You can edit it in Cloud Foundry Environment Cockpit of your subaccount.
In SAP Cloud Platform Transport Management, you can now use the destination to configure your transport
landscape.
Next Steps
Create Transport Nodes [page 35]

5.3 Create Transport Nodes
In SAP Cloud Platform Transport Management, transport nodes represent source and target end points of a
deployment process - for example, a Neo subaccount. Transports take place between transport nodes.
Prerequisites
● You have configured destinations. For more information, see Create Transport Destinations [page 32].
● You have one of the roles Administrator or LandscapeOperator assigned to your user. For more information,
● You are on your SAP Cloud Platform Transport Management home screen.
● If you want to use SAP Cloud Platform Alert Notification Service to send notifications about import actions,
ALERT_NOTIFICATION_SERVICE destination must be configured in the subaccounts where you want to
use it.
Procedure
1. You have the following options to create transport nodes:
○ Choose Landscape Visualization from the navigation pane, and then choose  (Create a Node).
○ Choose Landscape Wizard from the navigation pane, then select a template for your landscape, and
create your transport nodes as part of the process.
○ Choose Transport Nodes from the navigation pane, and choose  (Create a new node).
2. Enter a Name for the node, and a Description (optional) .
3. If you want to enable the upload of files to this node, select the Allow Upload to Node checkbox.
If you select the checkbox, you can add files to this node. It is also possible that external applications
upload files using API remote calls. If the checkbox isn´t selected, SAP Cloud Platform Transport
Management prevents the upload of files to this node.
4. If the ALERT_NOTIFICATION_SERVICE destination is configured in the subaccount, you can select the
Perform Notification checkbox.
If Alert Notification Service is configured, it issues notifications when an import on this node is started and
when it is finished. For more information, see Receive Notifications for Import Actions Using SAP Cloud
Platform Alert Notification [page 60].
5. You can select a Forward Mode.
By default, the value is set to Auto. In this case, 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 is started.
If you want to manually forward transport requests for this node, set the Forward Mode to the value Manual.
In this case, a Forward button appears in the import queue of this node. You can choose which transports
to forward later.

6. If you want to create a transport node pointing to a target end point of a deployment process, select the
content type that will be imported into this node, and the destination that will be used for the import. You
can select the available entries from the dropdown boxes.
The following content types are available:

○ Multitarget application (MTA)
○ XSC Delivery Unit
○ Application Content
If you want to create a source node of a transport, you can leave the Content Type and Destination fields
deselected.
7. If you want to create new destinations, use the Go to Destination View link to open the Destination view of
your subaccount in Cloud Foundry Environment Cockpit.
Results
The transport node was created.
You have the following options:
● You can edit transport nodes at a later point in time.

○ On the Transport Nodes screen, select the checkbox in front of the transport node name, and choose 
(Edit).
○ On the Landscape Visualization screen, select a transport node and click on the  (Edit Node) icon in
the side menu, or on the  (Edit) icon in the icon bar.
● You can navigate to the import queue of this transport node:
○ On the Transport Nodes screen, click anywhere in the transport node row.
○ On the Landscape Visualization screen, select the node, and choose the (Go to this node´s import
queue) icon.
● You can display the transport routes to which the transport node is assigned:
○ On the Transport Nodes screen, click anywhere in the transport node row, and choose the TRANSPORT
ROUTES tab.
○ On the Landscape Visualization screen, select the node, choose the (Go to this node´s import queue)
icon, and choose the TRANSPORT ROUTES tab.
You can check the details of all actions performed on nodes in the Landscape Action Logs [page 53].
Next Steps
Create Transport Routes [page 37]

5.4 Create Transport Routes
In SAP Cloud Platform Transport Management, transport routes are used to connect transport nodes.
Prerequisites
● You have configured transport nodes. For more information, see Create Transport Nodes [page 35].
● You have one of the roles Administrator or LandscapeOperator assigned to your user. For more information,
● You are on your SAP Cloud Platform Transport Management home screen.
Context
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.
Procedure
1. You have the following options to create transport nodes:
○ Choose Landscape Visualization from the navigation pane, and then choose  (Create a Route), or
select a transport node and choose  (Create Route) from the side menu.
○ Choose Landscape Wizard from the navigation pane, then select a template for your landscape, and
create your transport routes as part of the process.
○ Choose Transport Routes from the navigation pane, and choose  (Create a route).
2. On the following screen, enter a name for the transport route, and a description (optional). Choose the
source and the target nodes from the existing transport nodes.
Results
The transport route was created. You can edit transport nodes at a later point in time:
● On the Transport Routes screen, select the checkbox in front of the transport route name, and choose 
(Edit a route).
● On the Landscape Visualization screen, select a transport route and click on the  (Edit) icon in the icon
bar.
You can check the details of all actions performed on transport routes in the Landscape Action Logs [page
53].

5.5 Use the Transport Landscape Wizard
You can use the Transport Landscape Wizard to configure the transport nodes and transport routes of simple
transport landscapes.
Prerequisites
● You have configured transport destinations. For more information, see Create Transport Destinations [page
32].
● You have one of the roles AdministratorLandscapeOperator assigned to your user. For more information,
see or Security [page 56].
Procedure
1. On the SAP Cloud Platform Transport Management home screen, choose Access Wizard under Landscape
Management.
2. Under Selection of Template, select the number of transport nodes of which your landscape will consist.
A transport node represents the source or the target end point of a deployment process - for example, a
source (DEV) and a target (PROD) Neo account. For this scenario, you need a two-node landscape. If you
have an additional TEST account, you need a three-node landscape. For more examples, see also SAP
Cloud Platform Transport Management Scenarios [page 29].
3. Choose Next.
4. Enter names for the transport nodes and descriptions (optional).
5. If you want to allow that uploads can be made to this node, select the Allow Upload to Node checkbox.
This is required in the scenario where you want to transport archives that are available on a local file
system.
6. Optional: Select a Forward Mode.
By default, the value is set to Auto. In this case, 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 is started.
If you want to manually forward transport requests for this node, set the Forward Mode to the value Manual.
In this case, a Forward button appears in the import queue of this node. You can choose which transports
to forward later.
7. If you want to create a transport node pointing to a target end point of a deployment process, select the
content type that will be imported into this node, and the destination that will be used for the import. You
can select the available entries from the dropdown boxes.
If you want to create a source node of a transport, you can leave the Content Type and Destination fields
deselected.
8. If you want to create new destinations, use the Go to Destination View link to open the Destination view of
your subaccount in Cloud Foundry Environment Cockpit.

For more information, see Create Transport Nodes [page 35] and Create Transport Destinations [page 32].
9. Change the generated names of the transport routes so that you can later identify your transport routes,
and enter descriptions (optional).
For more information, see Create Transport Routes [page 37].

10. Choose Next.
The next screen shows the steps involved in the generation of the transport landscape.
11. Choose Summary.
On the Summary screen, you see a summary of the transport nodes and transport routes that you created.
You can directly go to the nodes or transport routes that you created through the links provided in the
Summary.
12. To close the wizard and return to the home screen, choose Finish.
Results
You have configured transport nodes and transport routes for your transport landscape. If required, you can
edit the individual entities.
For more information, see:

5.6 Create Destinations to SAP Cloud Platform Transport

Management
If you use SAP Cloud Platform Transport Management to transport content archives directly in another
application, the other application must be able to call the export API of the SAP Cloud Platform Transport
Management.
Context
To do so, destinations must be configured in the source subaccount of the other application that contain the
connection details given by the service key of the SAP Cloud Platform Transport Management instance.
For more information about how to get the details from the service key, see Set Up the Environment to
Transport Content Archives directly in an Application [page 15].
If the other application runs in the SAP Cloud Platform Neo environment, the destinations must point to the
Solutions Lifecycle Management Service.

One destination is required for the direct communication with SAP Cloud Platform Transport Management.
Another destination is required for the authentication of the technical user that is used for this direct
communication.
For more information about how to configure the destinations, see Setting Up Direct Uploads of MTA Archives
Using the Transport Management Service.
For SAP Cloud Platform Integration content, see also Content Transport Using Transport Management Service .

6 Using the Landscape Visualization
Use the Transport Landscape Visualization to configure the transport nodes and transport routes of your
transport landscape, as well as display and edit the existing landscape.
Prerequisites
● You have configured transport destinations. For more information, see Create Transport Destinations [page
32].
● You have one of the roles Administrator, or LandscapeOperator assigned to your user. For more
information, see Security [page 56].
Context
Use the Transport Landscape Visualization to perform the following tasks:
● Configure the transport nodes and transport routes of your transport landscape.
● Display and edit the existing transport landscape.
● Get an overview of the status of existing imports in the transport nodes.
Procedure
1. On the SAP Cloud Platform Transport Management home screen, choose Landscape Visualization from the
navigation pane.
All transport nodes and transport routes that are known in SAP Cloud Platform Transport Management are
displayed on the canvas. For all nodes, the import status is displayed. If the status is error or fatal, the node
is marked in red.
2. On the icon bar, the following functions are available:
Option Description
 (Create a Node) You can create a new transport node. A dialog box will open where you can enter all
relevant information for the node.
See Create Transport Nodes [page 35].
 (Create a Route) You can create a new transport route to connect transport nodes. A dialog box will
open where you can enter all relevant information for the route.
See Create Transport Routes [page 37].

Using the Landscape Visualization PUBLIC 41
Option Description
 (Edit) This function is active if you have selected a transport node or route in the canvas.
You can edit the selected node or route.
 (Delete) This function is active if you have selected a transport node or route in the canvas.
You can delete the selected node or route.
 (See properties) You can display and hide additional properties of a transport node or transport
route, such as the description, content type, or destination.
The properties are displayed in a separate panel on the right side of the screen. Se
lect a node or a route on the canvas to display its properties.
In the Properties panel, you have the following options for transport nodes:
Option Description
 (Create a job schedule) Opens the job scheduler that allows you
to schedule import jobs at regular inter
vals. See Schedule Imports [page 49].
Go to this node´s import queue Opens the import queue of the selected
transport node.
 (Refresh graph) You can refresh the graph, for example, to display changes made to the transport
landscape by other users.
 (Search) Enter any character string in the Search field to display a dropdown list of all trans
port nodes and routes (called Lines here) that match this string. If you select a node
or a route, it will be highlighted in blue.
 (Legend) You can display a legend of the colors used for the nodes and routes (called Lines in
the legend) on the canvas. If you click on an entry in the legend, all relevant entities
are highlighted in blue on the canvas.
 (Zoom In) You can use the functions to zoom to the required size of the transport nodes and
routes displayed on the canvas.
 (Zoom Out)
 (Zoom to Fit) You can automatically fit all transport nodes to the canvas.
 (Enter Full Screen) If you have large transport landscapes, you can display the canvas in full-screen
mode.
To exit full-screen mode, choose  (Exit Full Screen).
3. For a selected node, you have the following options using the icons in the menu next to each node:
Option Description
 (Create Route) You can create a new transport route to connect the selected transport node with a
target node. A dialog box will open where you can enter all relevant information for
the route. The selected node is preconfigured as source node.
See Create Transport Routes [page 37].
(Go to this node´s import You can open the import queue of the selected transport node.
queue)
See Using the Import Queue [page 44].
 (Edit Node) You can edit the selected node.

42 PUBLIC Using the Landscape Visualization
Option Description
See Create Transport Nodes [page 35].
 (Delete Node) You can delete the selected node.
As an alternative, you can use your keyboard´s Delete key.
4. For a selected route, you have the options to edit and delete the route using the icons in the icon bar.

Using the Landscape Visualization PUBLIC 43
7 Using the Import Queue
You start the upload of a file or an import process in the import queue of a transport node.
Prerequisites
Depending on the action that you want to perform in the import queue, you need one of the authorizations
available for Transport Management. For more information, see Security [page 56].
Procedure
1. On the Transport Management home screen, choose Transport Nodes from the navigation pane.
2. On the Transport Nodes screen, choose the transport node where you want to go to the import queue.
3. In the import queue, you have the following options:
○ Search and Filter Options

You can search the queue entries in the import queue by their transport description or status by
entering any character string in the Search field, or filter them according to the following criteria:
Filter Criterion Description
Status By default, queue entries with the statuses Initial, Repeatable, Fatal, and
Running are displayed. You can select or deselect status values from the
dropdown list.
 Note
All queue entries that have the status Succeeded or Error will automati
cally get the status Deleted after 30 days, the next time when an import
is started.
Preset Date Range By default, the queue entries of the last 7 days are displayed. You can select
different time intervals from the dropdown box. The timestamp of a queue
entry refers to the time of the last status change of the queue entry.
Custom Date You can select a date or a date range from the calendar by choosing 
(Open Picker)and clicking on the first and the last date of the date range. If
you have selected a date range, the value of the preset date range is greyed
out and no longer relevant. To clear the date range and return to the preset
date range selection, delete the dates from the entry field.

44 PUBLIC Using the Import Queue
You can reset all filter options to the default values by choosing Restore.
○ The transport requests are displayed in the import queue together with their description, owner,
status, and node in which they were added to the queue (Entry Node). For each transport request, you
have the following options:
Icon Description
 (See this transport request's You can display the name of the attached file.
content information)
For .mtar files, you can display additional information about the content
of the file.
 (Display the logs for queue entry) You can display the transport action log of the selected transport request.
○ Add
If you use Transport Management in the scenario Transport of Content Archives that are available on
Local File Systems: You can upload a file from your file system to the import queue for transport nodes
with the Allow Upload to Node checkbox selected.
For more information, see Add Files to Import Queues [page 46].
○ Import All, or Import Selected
You can either import all transport requests in an import queue, or selected transport requests only.
For more information, see Import Transport Requests [page 47].
○ Forward
If the Forward Mode of the transport node is set to the value Manual, you can manually forward
selected transport requests in this node to the target transport nodes according to the transport
routes defined for the node where the import is started.
You can forward transport requests in status Succeeded, Warning, and Error.
The transport requests are forwarded in the same order in which you selected them. Like this, you can
influence the order in which the transport requests are placed in the target import queue.
○ Reset
You can reset the status of selected queue entries in status Error and Succeeded to be able to repeat
the import of this entry.
○ Remove
You can remove selected queue entries from the import queue.
○ Schedule Imports
You can use the  (Import Scheduler) to configure Transport Management to schedule imports of all
transport requests at regular intervals. If imports are scheduled, the header area displays an IMPORT
SCHEDULE DETECTED button. You can click on this button to display more information about the job
status and the next execution time of the job. For more information about job scheduling, see Schedule
Imports [page 49].
○ Add MTA Extension Descriptors
You can customize the MTA deployment for a specific transport node using MTA extension descriptors.
To do this, in an import queue of a transport node of Cloud Foundry Environment, use  (Open MTA
Extension Descriptors). For more information, see Upload MTA Extension Descriptors [page 50].

Using the Import Queue PUBLIC 45
7.1 Add Files to Import Queues
By adding a file to the import queue, you upload it to the import queue and create a transport request.
Prerequisites
● You have one of the roles Administrator or ExportOperator assigned to your role. For more information, see
Security [page 56].
● You are using SAP Cloud Platform Transport Management in the scenario Transport of Content Archives
that are available on Local File Systems. For this, you have selected the Allow Upload to Node checkbox for
the transport node to which you want to add a file.
● You are in the import queue of the transport node where you want to add files. For more information, see
Using the Import Queue [page 44].
Context
In an import queue of a transport node, you can add content archives that you want to import. If you do this, a
transport request is created and it is added to the import queue of the transport node.
 Note
You only need to upload files if you transport content archives that are available on a local file system. If you
transport content archives directly in an application, the application adds them to the import queue.
You can upload files up to a maximum size of 400 MB. For each SAP Cloud Platform Transport Management
subscription, you can upload files with a total maximum size of 10 GB. You can check how much of your space
quota is already in use by selecting the drop-down arrow next to your user name and choose My File Quota.
If you upload larger files and depending on your network connection, the upload process can take some time.
To monitor the progress of the upload process, you can choose (Progress details on your current file
uploads). The progress of all file uploads of your user in the current browser session is displayed.
 Note
After an uploaded file was imported in all transport nodes along the configured transport routes, and the
queue items are not in one of the statuses Inital, Repeatable, or Fatal, SAP Cloud Platform Transport
Management automatically deletes the uploaded files after thirty days. The metadata of the transport
request is not deleted, only the file. The file is also automatically deleted if the transport request is deleted.
Like this, SAP Cloud Platform Transport Management ensures that the total maximum size of 10 GB is not
easily reached.

Procedure
1. In the import queue, choose Add.

2. In the Upload a file dialog box, enter the following details:
Field Description
Transport Description Description of the file upload process
Content Type If a transport destination is assigned to the transport

node, the content type is preselected based on the con
tent type specified in the destination. You cannot change
it. If no transport destination is assigned, you must select
the content type that you want to upload from the drop
down list.
File Select the file that you want to upload. For content type
Multitarget application, you can upload *.mtar files. For
content type XSC Delivery Unit, you can upload *.tgz
files. For application-specific content types, you can up
load .zip files.
3. To upload the file, choose OK.
The uploaded file is added to the import queue.
You can now import it.
Related Information
SAP Cloud Platform Transport Management Scenarios [page 29]
7.2 Import Transport Requests
You can either import all transport requests in an import queue, or selected transport requests only.
Prerequisites
● To execute an import of all transport requests in the import queue, you need the ImportOperator
authorization. To execute an import of selected transport requests in the import queue, you need the
TransportOperator authorization. For more information, see Security [page 56].

● You are in the import queue of the transport node where you want to execute imports. For more
information, see Using the Import Queue [page 44].
Context
All entries with the Initial, Fatal, and Repeatable statuses can be imported.
Procedure
1. In the import queue, you have the following options:
○ Choose Import All.

All queue entries are imported in the sequence in which they are placed in the import queue.
○ Select the transport requests that you want to import, and choose Import Selected.
Only the selected transport requests are imported in the sequence in which they are placed in the
import queue.
Note that the import of individual transport requests can lead to inconsistencies in the target runtime if
dependent transport requests are not imported. SAP Cloud Platform Transport Management does not
perform any dependency checks on the selected transport requests.
2. By default, the import will be executed immediately.
You can also schedule imports of all transport requests to be executed at regular intervals. For more
information, see Schedule Imports [page 49].
When an import is started, and the Forward Mode of the transport node where the import was started is set
to Automatic (default value), the first action that SAP Cloud Platform Transport Management performs is
forwarding all transport requests to be imported to the target transport nodes according to the transport
routes defined for the node where the import is started.
The forwarded transport requests are added to the end of the import queues of the target transport nodes.
If the forwarded transport requests are already part of the import queue of the target node, they are moved
to the end of this import queue. The status of a moved transport request will change as follows:
○ Initial will remain Initial.
○ Succeeded, Error, Fatal, Deleted, and Warning will change to Repeatable.
○ Repeatable will remain Repeatable.
Results
If the transport node has a content type and a valid destination assigned, the transport requests are imported
into the runtime of the transport node. If the import fails, the transport requests will still be forwarded to the
import queues of the target nodes.
 Note
If a transport request with a Multitarget Application archive (.mta) was imported in a subaccount of the
SAP Cloud Platform Neo environment, the archive will afterward be visible in the Standard Solutions

category in the Solutions page in the cloud cockpit of the subaccount. For more information on solutions,
see Operating Solutions in the SAP Cloud Platform documentation.
7.3 Schedule Imports
If you want to execute imports of all transport requests of a transport node, you can schedule them at regular
intervals.
Prerequisites
● To schedule imports, you need the TransportOperator authorization. For more information, see Security
[page 56].
● You are in one of the following places in SAP Cloud Platform Transport Management:
○ In the import queue of a transport node
○ In the Properties panel of a transport node in the Landscape Visualization
Procedure
1. Choose  (Import Scheduler).

2. In the dialog box, you can choose one of the import patterns Daily or Weekly:
Option Description
Daily Choose a time interval for the scheduled daily imports

from the dropdown box (for example, Every hour, Four
times per day).
Weekly You have the following options:

○ Select a time interval for the scheduled weekly import
from the dropdown box (for example, Every week,
Every second week.
○ Select an Execution Time, that is the starting time, for
the scheduled imports.
○ Select the days of the week on which the scheduled
imports take place.
3. By default, the import schedule is inactive. To activate the schedule, select the Schedule is inactive
checkbox. The text will change to Schedule is active.
4. Choose Create.

Results
If the schedule is active, the imports of all transport requests in the import queue of the transport node are
scheduled with the specified options and will be executed as specified.
If you start an import queue with scheduled imports, the header area displays an IMPORT SCHEDULE
DETECTED button. You can click on this button to display more information about the job status and the next
execution time of the job.
 Note
If the job scheduler has a lot of jobs to process, it is possible that the start time of the job is delayed.
7.4 Upload MTA Extension Descriptors
If an extension descriptor file exists for a Multitarget Application (MTA) that you want to import, you can upload
it in the import queue of the corresponding transport node of Cloud Foundry Environment.
Prerequisites
● To upload or delete MTA extension descriptors, you need the TransportOperator authorization. For more
information, see Security [page 56].
● You are in the import queue of a Cloud Foundry transport node for the Content Type Multi-Target
Application in Transport Management.
Context
 Note
This function is supported for transports in Cloud Foundry Environment only.
A Multitarget Application (МТА) extension descriptor is a file that contains data complementary to a
deployment descriptor. It allows you to customize the MTA deployment for a specific transport node. The file
has the extension .mtaext. You can upload it in the import queue of a transport node. The MTA extension
descriptor is used at import time whenever a transport request that contains a matching MTA version is
imported. The following conditions must be met so that an MTA extension descriptor matches an MTA version:
● The MTA ID is the same as specified using the extends: parameter in the MTA extension descriptor file.
● The version binding defined for the MTA extension descriptor in Transport Management matches the
version of the MTA that is imported.
You can upload an MTA extension descriptor in an import queue at any point in time before the import of the
MTA, also before the MTA itself is added to the import queue. It is used at the time of the import.

If you use MTA extension descriptors, you must upload them in every import queue of every transport node
into which you want to import the transport request that contains the MTA. MTA extension descriptors are not
forwarded to any target nodes.
For more information about how to define MTA extension descriptors, see Defining MTA Extension Descriptors.
Procedure
1. Choose  (Open MTA Extension Descriptors).
In the dialog box, you see a list of MTA IDs for which MTA extension descriptors were already uploaded in
the current import queue, together with the version binding defined for them, and the description.
2. In the dialog box, you can upload a new extension descriptor. To do this, choose Add.
a. In the Add a new MTA Extension Descriptor dialog box, enter the following details:
Field Description
MTA Extension Click anywhere in the input field, or choose Browse... to select the MTA extension descriptor that
File you want to upload in the import queue.
Version Binding You can define for which versions of the MTA you want to use the extension descriptor.
If you have uploaded an MTA extension descriptor, by default, this field contains an asterisk (*).
This means that the MTA extension descriptor is valid for all versions of the MTA.
 Recommendation
We recommend that you leave the asterisk unchanged.
If you want to define that the MTA extension descriptor is valid for a specific version of the MTA
only, you can enter the version of the MTA for which the extension descriptor is valid, for exam
ple, 1.4.2.
 Note
You cannot use a combination of both options, for example 1.4.*.
However, you can have both an extension descriptor that is valid for all versions of an MTA,
and extension descriptors for specific versions of the MTA. If both exist for a specific ver
sion, Transport Management will use the specific extension descriptor at for the import.
Description By default, the name of the uploaded MTA extension descriptor file is entered as the description.
You can change it.
b. Choose Submit new descriptor.
The MTA extension descriptor that you uploaded is now available in the import queue. It is used when the
transport request with the matching MTA version is imported.
3. In addition, in the MTA Extension Descriptors dialog window, you have the following options:

Task How To
Show the content of an MTA ex Choose  (Show file content).

tension descriptor file that was al
ready added to the import queue.
Download an existing extension Choose  (Download MTA Extension File).

descriptor.
Remove a selected extension de Select the extension descriptors that you want to remove, and choose Remove.
scriptor from the import queue. The file will be removed.
Next Steps
You can check whether an MTA extension descriptor exists for an existing MTA in the import queue by choosing
 (See this transport request's content information). If an MTA extension descriptor exists, the  (An extension
descriptor is available for the Multi-Target Application archive.) icon is displayed next to the name of the .mtar
file. You can expand the tree to display the MTA ID.
The actions uploading and deleting MTA extension descriptors are reflected in the transport action logs. When
an extension descriptor is used for an import of an MTA, the transport action logs also contain information
about the extension descriptor used.

8 Landscape Action Logs
The landscape action logs display the history of all actions related to landscape configuration.
This includes actions such as create, edit, and delete transport nodes, transport routes, and scheduled import
jobs.
The log displays a list of landscape actions sorted according to the time when the action was performed. The
most recent action is at the top. For each action, it contains information about the user and, for each Edit
action, it contains the data from the previous state (Old value) and the new state (New value). For Create or
Delete actions, one of the states Old value or New value is always None.
You can filter the columns Type, Action Type, and User by entering any character string in the Search field. Note
that you cannot use the Search field for text displayed in any of the other columns.

Landscape Action Logs PUBLIC 53
9 Transport Action Logs
The transport action logs display a history of all actions related to the transport.
Transport Action Logs
The following are transport actions:
● Import to Node
● File Upload
● Upload to Node
● Delete Queue Entry
● Repeat Queue Entry
● Export to Node
● Add Queue Entry
● Forward Queue Entry
The log displays a list of transport actions sorted according to the time when the action was performed. The
most recent action is at the top. For each action, it contains information about the node, action type, user,
status, and the end time. You can display detailed information about the individual actions by clicking in the
respective line.
In the Transport Action Logs, you can do the following:
● Filter the data in the log columns Node, Action Type, User, Status, and End Time either by entering any
character strings in the respective fields and choosing Enter , or choosing the relevant information from
the dropdown boxes.
● Navigate to a detailed Log of Action for a specific transport action by clicking anywhere in the row of the
transport action.
● Refresh expired transport actions by choosing the relevant link. These are actions which are in status
Running, but which haven´t been updated in a long time.
● Download all transport actions to a .zip file by choosing  (Download all transport action logs). The .zip
file contains one .txt file for each transport action.
● Refresh the status of import actions that are currently running by choosing Refresh expired actions. By
default, SAP Cloud Platform Transport Management refreshes the status of import actions that remain for
too long in the Running status at regular intervals when you are in the import queue of the transport node.
Here, you can manually trigger a refresh.
Log of Action: <Transport Action>
In the detailed view, you find a detailed log for a specific transport action.

54 PUBLIC Transport Action Logs
In the Log of Action: <Transport Action>, you can do the following:
● Filter the messages by entering any character string in the Messages field. In addition, you can narrow
down the results according to Transport Request, Transport Status, Content, and Message Severity by
choosing the relevant criteria from the dropdown boxes.
● Download all messages of an action to a text file by choosing  (Download transport logs).
 Note
The log of a transport request which is displayed when you choose the  (Display the logs for queue entry)
icon in the import queue, contains all transport actions for this transport request. You cannot download the
transport log for a transport request.

Transport Action Logs PUBLIC 55
10 Security
This section describes the security aspects that are relevant for SAP Cloud Platform Transport Management.
SAP Cloud Platform Transport Management Role Templates
SAP Cloud Platform Transport Management delivers the following role templates that you can use to create
user roles to enable access to specific tasks.
Role Template Description
Administrator Contains the overall administration authorization for all SAP Cloud Platform Transport
Management tasks. The Administrator has all authorizations of the other roles, as well as
additional authorizations. In the import queue, the Administrator can add files to the import
queue, remove files from the import queue, and reset the status of queue entries. If the
Forward Mode of a transport node is set to the value Manual, the Administrator can forward
all or selected transport requests to the target import queue.
TransportOperator Grants authorizations for removing files from the import queue, resetting the status of
queue entries, and forwarding queue entries, as well as uploading and deleting MTA exten
sion descriptors, and scheduling imports.
This role also includes authorizations for import tasks (ImportOperator), plus starting the
import of selected transport requests.
ExportOperator Grants authorizations for export tasks. This includes adding files to import queues, and, if
files are transported directly in the application, adding them to a transport request in the
application.
ImportOperator Grants authorizations for import tasks. This includes starting the import of all transport re
quests in the import queue.
This role doesn’t include authorizations for importing selected transport requests, adding
files to the import queue, removing files from the import queue, resetting the status of
queue entries, and forwarding queue entries.
LandscapeOperator Grants authorizations for transport landscape configuration tasks. This includes creating
transport nodes and transport routes, as well as editing, and deleting them. It also includes
displaying the landscape action logs.
Viewer Grants display authorization in SAP Cloud Platform Transport Management. This role
doesn’t include authorizations to perform any landscape configuration or import tasks.
For more information about how to use SAP Cloud Platform Cockpit to create roles and role collections to
which you can assign these role templates, see Building Roles and Role Collections for Applications.

56 PUBLIC Security
Transport Node-Specific Attributes
For the role templates TransportOperator, ExportOperator, and ImportOperator, attributes exist that allow you
to restrict the corresponding authorizations to specific transport nodes only.
The following attributes exist for SAP Cloud Platform Transport Management:
Role Template Attribute Name
TransportOperator TmsNodesTransportOperator
ExportOperator TmsNodesExport
ImportOperator TmsNodesImport
To do this, you create node-specific roles based on the role templates, and add the corresponding attributes to
the roles. You enter the transport node names as values of the attributes. For each attribute, you can enter one
or multiple transport node names.
For these restricted roles with attributes, the corresponding tasks can be performed only in the transport
nodes that were entered as attribute values.
 Note
When adding attributes to roles, it is not checked that the transport node names exist in your transport
landscape. Equally, when you delete a transport node, you must manually update the corresponding role, if
required.
If you don´t add any attributes to a role, this allows unrestricted access to all nodes. If you assign both
restricted and unrestricted roles to users, the restricted role takes effect.
For more information about how to use SAP Cloud Platform Cockpit to create roles with attributes, see
Attributes.
Audit Logs
SAP Cloud Platform Transport Management writes security-relevant events to the audit log. You can use the
Audit Log Viewer to view the audit log messages. SAP Cloud Platform Transport Management writes audit log
messages of category audit.security-events in the following situations:
Situation Audit Log Message
Error when calling a service endpoint without Authorization check for the scope <scope-name>
sufficient authorization failed...
Tenant subscription Tenant <tenant-id> was subscribed ...
Tenant unsubscription Tenant <tenant-id> was unsubscribed...
To access the Audit Log viewer, perform the following steps:
1. Subscribe to Audit Log viewer in the subaccount in which you’re subscribed to SAP Cloud Platform

Security PUBLIC 57
2. Assign the auditlog-management and auditlog-viewer roles to your role collection.
3. Call the subscribed Audit Log viewer. To do this, choose Go to Application in the Subscription view of your
subaccount in SAP Cloud Platform Cockpit.
For more information, see Audit Logging in the Cloud Foundry Environment and Audit Logging in the Neo
Environment in the SAP Cloud Platform Security information.
Malware
The SAP Cloud Platform Transport Management service treats archives that it uploads, attaches, or transports
as ‘black box’ content. This means, SAP Cloud Platform Transport Management doesn’t process or extract any
archives. They’re only temporarily persisted as BLOB (Binary Large Objects) in the database. Therefore, SAP
Cloud Platform Transport Management doesn’t perform any malware scans, since it's the obligation of the
deploy target applications, services, or content runtimes which process the uploaded or referenced archive to
perform malware scans. The only exception is the transport of an MTA archive. Here, the SAP Cloud Platform
Transport Management service reads the metadata of the MTA, and ensures that the MTA archive contains a
malware-free MTA deployment descriptor file. However, the modules of the MTA itself aren’t covered by the
check since it´s again the obligation of the corresponding applications, services, or content runtimes which are
called with the module content to perform the malware scans.

58 PUBLIC Security
11 Integration
To propagate applications, or application-specific content using SAP Cloud Platform Transport Management in
an integrated way, you can make use of the SAP Cloud Platform Transport Management (TMS) Export API.
SAP Cloud Platform Transport Management (TMS) Export API offers operations for uploading a file to SAP
Cloud Platform Transport Management and to perform the export on a specified transport node. If a physical
file is transported, the File Upload is always the first operation, followed by Node Export, or Node Upload. It is
also possible to perform a transport based on a reference, where a file upload is not needed.
Use Node Export, if you want to enable the transport of content directly in your application. The previously
uploaded file or a specified reference is attached to a new transport request which is added to the import
queues of the follow-on transport nodes of the export node.
Use Node Upload in continuous integration scenarios, for example, where you have an external content or
application archive (MTA, for example) that you want to upload in the first transport node of your transport
landscape. You can also use it to upload content or applications to a specific subaccount that is not part of your
standard transport landscape, for example a training subaccount.
If you want to use the TMS Export API, perform the following steps:
1. Create a package that contains your content.

2. Call the SAP Cloud Platform Transport Management File Upload API (only required for file-based
transport).
3. Depending on your use case, call one of the following SAP Cloud Platform Transport Management APIs and
pass the ID of the uploaded file (or the reference, for reference-based transport):
○ Node Export
○ Node Upload
For more information about the SAP Cloud Platform Transport Management Export API, see SAP API Hub at
https://api.sap.com/api/TMS_v2/resource .

Integration PUBLIC 59
12 Receive Notifications for Import Actions
Using SAP Cloud Platform Alert
Notification
You can configure SAP Cloud Platform Transport Management to send notifications for import actions using
SAP Cloud Platform Alert Notification Service.
Prerequisites
● You have an active subscription for Transport Management.

● Your global account and subaccount are entitled for SAP Cloud Platform Alert Notification (Alert
Notification, for short).
Context
If there’s a service instance of Alert Notification available in the Cloud Foundry subaccount in which you’re
using Transport Management, you can configure the ALERT_NOTIFICATION_SERVICE destination, which
refers to the service instance. This enables Alert Notification to send notifications for import actions of
Transport Management. In addition, you create the subscription for receiving notifications in any channel that
Alert Notification supports, by e-mail, or Slack channel, for example.
For more information about Alert Notification, see SAP Cloud Platform Alert Notification.
Procedure
1. In the Cloud Foundry space of the subaccount in which you’re using Transport Management service, in SAP
Cloud Platform Cockpit, navigate to the Service Instances page, and create a service instance for Alert
Notification service as described under Initial Setup in the Alert Notification documentation.
Under step 8. Obtain the credentials for the Alert Notification service, choose option b. Create a Service Key
from the Service Key tab to make the service instance URL and credentials available to you for accessing
the service using the Transport Management service.
2. In SAP Cloud Platform Cockpit of the subaccount in which you’re using Transport Management service,
use the Destination service to create a destination with the fixed name ALERT_NOTIFICATION_SERVICE.
a. Choose Connectivity Destinations New Destination .

b. Enter the following details:

60 PUBLIC Receive Notifications for Import Actions Using SAP Cloud Platform Alert Notification
Field Input
Name Enter ALERT_NOTIFICATION_SERVICE.
Type Choose HTTP.
Description (optional) You can enter a description for the destination.
URL Enter the value of the url attribute from the Service Key of the service instance cre
ated in step 1.
Proxy Type Choose Internet.
Authentication Choose OAuth2ClientCredentials.
Client ID Enter the value of the client_id attribute from the Service Key of the service in
stance created in step 1.
Client Secret Enter the value of the client_secret attribute from the Service Key of the service in
Token Service URL Enter the value of the oauth_url attribute from the Service Key of the service in
3. To enable the notifications for a transport node, in Transport Management service, when creating a
transport node, select the Perform Notification checkbox.
If the checkbox is grayed out, this means that the destination wasn’t configured.
See also: Create Transport Nodes [page 35]

4. In SAP Cloud Platform Cockpit, set up the way in which you want to receive notifications. For more
information, see Managing Subscriptions in the Alert Notification documentation.
a. To register the relevant event, the following conditions are available for Transport Management service:
○ TmsImportStarted
○ TmsImportFinished
 Example
Select the notation element eventType and the operand Is Equal To, and set the expected
value to TmsImportStarted.
In this example, you will get notifications for every import that is started in your landscape.
b. You can set additional conditions by selecting the notation element tags.<option>.
You can enter one of the following options:
Option Description
nodeId ID of the transport node where the import action was triggered
nodeName Name of the transport node where the import action was triggered
user Name of the user that triggered the import action
actionId ID of a transport action

Receive Notifications for Import Actions Using SAP Cloud Platform Alert Notification PUBLIC 61
 Example
Select the notation element tags. and complete the element by adding user. Select the operand
Is Equal To, and set the expected value to an existing user name, for example:
lily.doe@company.com.
If you use this condition in addition to the condition set in the previous examaple, you will get
notifications for every import that is started in your landscape by lily.doe@company.com.

62 PUBLIC Receive Notifications for Import Actions Using SAP Cloud Platform Alert Notification
13 Data Protection in SAP Cloud Platform
Transport Management
Introduction to Data Protection
Data protection is associated with numerous legal requirements and privacy concerns. In addition to
compliance with general data privacy acts, it is necessary to consider compliance with industry-specific
legislation in different countries. This section describes the specific features and functions that SAP provides
to support compliance with the relevant legal requirements and data protection in SAP Cloud Platform
This section does not give any advice on whether these features and functions are the best method to support
company, industry, regional or country-specific requirements. Furthermore, this section does not give any
advice or recommendations with regard to additional features that would be required in a particular
environment; decisions related to data protection must be made on a case-by-case basis and under
consideration of the given system landscape and the applicable legal requirements.
 Note
In most cases, compliance with data privacy laws is not a product feature. SAP software supports data
privacy by providing security features and specific data-protection-relevant functions such as functions for
the simplified blocking and deletion of personal data. SAP does not provide legal advice in any form. The
definitions and other terms used in this document are not taken from any given legal source.
 Caution
The extent to which data protection is ensured depends on secure system operation. Network security,
security note implementation, adequate logging of system changes, and appropriate usage of the system
are the basic technical requirements for compliance with data privacy legislation and other legislation.
Information specific for SAP Cloud Platform Transport Management
Some basic requirements that support data protection are often referred to as technical and organizational
measures (TOM). The following topics are related to data protection and require appropriate TOMs:
● Access control: Authentication features as described in section Security [page 56].

● Separation by purpose: Is subject to the organizational model implemented and must be applied as part of
the authorization concept.
Personal Data processed by SAP Cloud Platform Transport Management

SAP Cloud Platform Transport Management records all tenant changing processes, like landscape transports
and landscape configurations. They are recorded together with the user who performs the action and the time

Data Protection in SAP Cloud Platform Transport Management PUBLIC 63
when it was done. Doing so, the user is identified by its user ID, maintained in the configured identity provider
and used during login. Sensitive personal data is not processed by the service.
Personal Data Encapsulation

SAP Cloud Platform Transport Management ensures that tenant-specific content is stored in a separate
schema so that this data is not visible in other tenants.
View Personal Data

User information is shown in the SAP Cloud Platform Transport Management user interface and available using
a REST API, when the corresponding landscape-related or transport-related entities are requested.
Deletion of Personal Data

The tenant-specific and user-specific persistency as done by SAP Cloud Platform Transport Management is
related to the lifecycle of the tenant subscribed to the service. The records are required to fulfill auditability
requirements. The deletion of all data is performed as part of the unsubscription process.
 Note
In order to keep the data for the legally required retention period, the corresponding tenant-based
subscription to the SAP Cloud Platform Transport Management SaaS application must be in place.
Related Information
For more information about data protection in SAP Cloud Platform, see Data Protection and Privacy in the SAP
Cloud Platform documentation.

64 PUBLIC Data Protection in SAP Cloud Platform Transport Management
14 Monitoring and Troubleshooting
This section describes how you can get support if things start to go wrong.
Getting Support
If you encounter an issue with this service, we recommend that you follow the procedure below:
Check Platform Status

Check the availability of the platform at SAP Cloud Platform Status Page .
For more information about selected platform incidents, see Root Cause Analyses.
Check Guided Answers

In the SAP Support Portal, check the Guided Answers section for SAP Cloud Platform. You can find solutions
for general SAP Cloud Platform issues as well as for specific services there.
Contact SAP Support

You can report an incident or error through the SAP Support Portal. For more information, see Getting Support.
Please use the following component for your incident:
Component Name Component Description
BC-CP-LCM-TMS Transport Management for application content
When submitting the incident, we recommend including the following information:
● Landscape information (such as EU10, US10, AP10)

● The name of the affected SAP CP global account and the subaccount
● The URL of the page where the incident or error occurs
● The steps or clicks used to replicate the error
● Screenshots, videos

Monitoring and Troubleshooting PUBLIC 65
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

66 PUBLIC Important Disclaimers and Legal Information
Important Disclaimers and Legal Information PUBLIC 67
www.sap.com/contactsap
© 2020 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

SAP Cloud Platform Transport Management: User Guide - Public Document Version: 1.0 - 2020-06-08

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Cloud Platform Transport Management: User Guide - Public Document Version: 1.0 - 2020-06-08

Uploaded by

Copyright:

Available Formats

USER GUIDE | PUBLIC

Document Version: 1.0 – 2020-06-08

SAP Cloud Platform Transport Management

THE BEST RUN

1 What is SAP Cloud Platform Transport Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 What's New for Transport Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

4 SAP Cloud Platform Transport Management Home Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . .24

5 Configuring the Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

6 Using the Landscape Visualization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

7 Using the Import Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

8 Landscape Action Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

9 Transport Action Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

SAP Cloud Platform Transport Management

13 Data Protection in SAP Cloud Platform Transport Management. . . . . . . . . . . . . . . . . . . . . . . . 63

14 Monitoring and Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

SAP Cloud Platform Transport Management

The files can be transported in one of the following scenarios:

● Directly from within another application

It offers user interfaces that can be used in the following ways:

● Using a graphical user interface

For more information, see Initial Setup [page 14].

● Software-as-a-Service (SaaS) solution in Cloud Foundry with tenant separation

SAP Cloud Platform Transport Management

● Multitarget Applications in the Cloud Foundry Environment

SAP Cloud Platform Transport Management

SAP Cloud Platform Transport Management

2.1 2019 Transport Management (Archive)

SAP Cloud Platform Transport Management

SAP Cloud Platform Transport Management

SAP Cloud Platform Transport Management

SAP Cloud Platform Transport Management

SAP Cloud Platform Transport Management

2.2 2018 Transport Management (Archive)

SAP Cloud Platform Transport Management

SAP Cloud Platform Transport Management

1. Provide Access to SAP Cloud Platform Transport Management [page 14]

Provide access to SAP Cloud Platform Transport Management.

3. Configuring the Landscape [page 28]

3.1 Provide Access to SAP Cloud Platform Transport

SAP Cloud Platform Transport Management

3.2 Set Up the Environment to Transport Content Archives

Steps to use the User Interface of Transport Management

Step Action Video More Information

1. In your global account, choose an existing Cloud Create a Subaccount

2. Enable Cloud Foundry to create an organization Create Spaces

SAP Cloud Platform Transport Management

3. Subscribe to the Transport Management appli­ Getting Started with

The subscription is activated. The Go to

SAP Cloud Platform Transport Management

Step Action Video More Information

1. In your subaccount, choose Security Assign roles to role collections:

Role Collections New Role Collections .

All roles that are available for SAP Cloud

SAP Cloud Platform Transport Management

Step Action Video More Information

6. Assign an entitlement to Transport Configure Entitlements

2. Choose Entitlements Subaccount

6. To save the service plan, choose Save.

The service plan for Transport Management is

7. In the Cloud Foundry organization, create a Create Spaces

SAP Cloud Platform Transport Management

3. To assign the quota plan to your space, un­

9. In the space, create a service instance of Creating Service In­

3. Subscribe to the Transport Management appli Getting Started with

3. To assign the quota plan to your space, un

9. In the space, create a service instance of Creating Service In

2. Subscribe to the Transport Management appli Getting Started with