In any of SAP landscapes there can be hundreds or thousands of customization done in Development system which is needed to be transferred to Testing system or QA system for testing and then finally to Production system. The transport of these changes within a landscape is governed by concept known as Transport Management System.
The purpose of the TMS, accessed via transaction STMS, is to centrally control the propagation of changes through the system landscape based on predefined paths.
With TMS you are able to:
- Define an SAP system’s role within a system landscape or transport domain
- Configure the transport routes using either an editor or delivered standard configurations
- Configure the transport tool program’s (tp) parameter profile
- Display the import queues of all systems in the transport domain
- Define quality assurance / acceptance procedures in the QA system
- Schedule the import of change requests in an import queue
- Perform transports between systems without a common transport directory
- Handle transport proposals of developers
TMS thus enables system administrators to centrally manage the transport configuration of multiple systems by defining transport domains, assigning domain controllers and defining transport routes.
Transport Domain: Consists of all the systems which are managed through TMS.
Transport Domain Controller: It is the system where configuration of all the systems are maintained. Any changes in the landscape are distributed evenly amongst the landscape such that the configuration remains consistent throughout the landscape. Domain controller holds the reference configuration and all the other systems consists of copy of that reference configuration.
A system landscape is a set of systems that share customizing and repository objects via transported change requests. A transport domain can contain multiple system landscapes.
The configuration of TMS can be broken down into three individual steps.
1. Configuring the transport domain defines which systems will be included in the domain.
2. Configuring the transport routes defines the system and client roles within the landscape(s).
3. Configuring the QA procedure defines who is responsible for approving the acceptance of changes and the promotion of those changes to the delivery system(s).
The first system you configure is automatically selected as the transport domain controller but you may later switch the role of the domain controller to a different system.SAP recommends that the system chosen to be the domain controller have the following attributes:
- High security precautions
- Highest level of maintenance
When using TMS for the first time after system installation, you are automatically prompted to initialize the TMS. You must initialize the TMS while logged on to client 000. For configuring TMS you need the authorization S_CTS_ADMIN.
Transaction STMS in client 000 will:
- Assign the SAP system as the transport domain controller
- Create transport domain name DOMAIN_<SID>
- Create transport group GROUP_<SID>
- Create system user TMSADM in client 000
- Create RFC destinations
- Set up file DOMAIN.CFG in directory bin of the transport directory
When you initialize the TMS, the following actions will automatically be carried out by the SAP system:
- A transport group is created with the name GROUP_<SID>.
- In client 000, the system user TMSADM is created.
- The RFC destinations required for the TMS are generated.
- The TMS configuration file DOMAIN.CFG is stored in the transport sub directory bin. This file contains the transport domain name and description as well as the transport domain controller’s host name, instance number, SID, and transport group.
- The transport profile for the transport control program tp is generated and stored in the transport subdirectory bin under the name TP_<DOMAIN>.PFL. The parameters in this profile are maintained using the transaction STMS.
Addition of new system in transport domain
A new system is added into the transport domain using request for inclusion method. SAP system applies for inclusion into the transport domain and then domain controller approves the request. Once a system is added into the transport groups, then the information of transport domain is stored in Domain.cfg file in bin directory in shared path.When STMS in initialized it reads the Domain.cfg file and check what all systems are there in the domain and who is the transport domain controller. In case if the SAP system doesn’t have shared transport directory then we can add the settings manually.
In any case, when an SAP system has been configured for the TMS and approved in the domain, you will find a newly created user TMSADM and generated RFC destinations required for the TMS. Systems within a transport domain communicates with each other using RFC’s, and all the relevant RFC’s and users are created automatically by TMS tool only.There are two types of RFC destinations created by the TMS:
TMSADM@<SID>.<domain name> and TMSSUP@<SID>.<domain name>
The user TMSADM is inserted in the TMSADM RFC but not in the TMSSUP one. Scheduling a transport uses TMSSUP RFC so it prompts for user id and password.
Virtual systems are often included as place holders for planned systems and are replaced by the planned system after it is physically installed.
If the SAP System acting as the domain controller fails, no changes can be made to the TMS configuration. SAP therefore recommends that you configure a backup domain controller that can assume the function of the domain controller when required. It may also be necessary to move the transport domain controller to another SAP system. In such a case, you must activate the backup domain controller. Then, the backup domain controller becomes the domain controller and vice versa.
Look for Next tutorials to learn more about TMS.