STMS needs to be configured to export and import transport request across systems in the landscape. This can be obtained with the help of R3trans.exe and tp.exe which are located in the kernel of central instance. TMS should be configured as a part of post installation after CTS has initialized. In TMS configuration, we have to identify one of the systems as TDC in the landscape.
TDC acts as a leader for all the systems within a transport domain. TDC configures its local transport directly, /usr/sap/trans, as common transport directory for all the systems in transport domain and TDC allows configuration and administrative settings to be performed for other systems in the domain then changes distributed to all other systems.
Collection of all the systems connected together in TMS is called as Transport Domain. Usually development system configured as TDC instead of quality and production.
Usually once Dev server installed we have to configure TMS after CTS initialization, which should be done by configuration of TDC. As QAS and PRD systems are not yet installed in the initial stage of implementation, generally, DEV gets configured as TDC. Logon to DEV with DDIC in client 000, execute STMS after initializing CTS. Once STMS executed for the first time system asks for the transport domain name setup and information of domain controller. Once required information is given save the configuration. Note:-To configure current system as TDC that local system information no need to be given, instead save the configuration.
This file is a part of bin directory created after TMS configured which maintains TD information means all the systems information taken place in TD. Incase this file has been corrupted, has to be regenerated by TMS tool, but should not be edited manually.
It is a configuration file of transport domain resides in bin directory gets created by the system when TMS got configured. This transport profile TP_DOMAIN_SID.PFL, which contains all the system information includes SID, Common transport directory, DB type and DB information, etc… in terms of parameters and values. As per the configuration settings maintained in transport profile we are required to use different unconditional modes upon the requirement when importing a TR in to a specific system.
As per the initial stage of the implementation project, only DEV system get installed which will be configured as TDC. When developer customizes object and includes them in a TR that request should be routed to its target system where it gets imported. But as the target quality system would not be installed already .We are required to create other quality and production system as virtual systems in TMS configuration with same SID will be used in future installation of these systems. So that a transport request can be exported to its mentioned target which is quality automatically once it is released. Later once other quality and production systems are physically installed we can convert them as physical systems in TMS by specifying same TDC as it was configured and approving them through TDC.
Classification of all development objects as per its type which are standard and customized should be assigned with a transport layer which is standard and customized through which these objects gets exported/imported from integration to consolidation system. A transport layer configuration is a logical assumption because all the dev objects should be assigned with the transport layer either standard or customized. There is a standard layer “SAP” already exists in the system we need to create customized layer with Z<SID> format. Now two consolidation routes required to be created from integration to consolidation system with the assignment standard and customized layer. So that all standard objects will be moved through the standard layer, SAP, and customized objects moved through Z<SID> layer.
Logical route gets created between the systems taken place in transport domain through which we assume a TR can be export/import is called transport route. We have two types of transport routs in TMS 1. Consolidation route 2. Delivery route
The route obtained between integrated system and consolidation system is known as consolidation route.
The route obtained between consolidation system to recipient system is called as delivery route.
In case more than one system configured at consolidation level or recipient level, more than one consolidation route or delivery route cannot be created by assigning single transport layer. In this situation, grouping all consolidation systems with naming format /Name/ is called as target group. Now consolidation routes are targeting to this group, from the group to all the consolidation systems route obtained automatically so that a TR which has released an integrated system will be exported to all the systems in the group then can be imported into all.