SAP Basis Transport System continued

In the previous post we are discussing about  SAP Basis Change and Transport System Pre Requirements and here is the continuation for that.
Initializing the Transport Domain Controller 
To activate the TMS on an R/3 System, run Transaction STMS in client 000 with user  authorization S_CTS_ADMIN.If the R/3 System is already assigned to a transport  domain, the TMS initial screen shows the system's status, either as a domain controller, or as an R/3 System within a domain. If the R/3 System is not yet assigned to a transport domain, R/3 tries to locate an existing transport domain within the current transport group by reading the file DOMAIN.CFG in the directory bin of the common transport directory. If no transport domain exists, a new transport domain is created, and the current R/3 System is assigned as the transport domain controller.  When a transport domain controller is first created, the TMS generates:

A transport domain and a transport group
ŸThe RFC destinations required for the TMS
ŸFile DOMAIN.CFG in directory bin of the common transport directory, for storing the TMS configuration
The name of the transport domain may not contain blanks and may not be changed afterwards without reconfiguring the domain controller. By default, a transport domain will have the name DOMAIN_, where is the system ID of the domain controller.
Adding Additional R/3 Systems to a Domain
After configuring an R/3 System as the transport domain controller, each additional R/3 System must apply for inclusion to the transport domain controller. The transport domain controller then must confirm inclusion for each R/3 System. The initial screen of Transaction STMS indicates if an R/3 System is waiting for inclusion in the transport domain.

After you have included an R/3 System from one of the transport groups in the transport domain, the description of the transport domain is stored in the file DOMAIN.CFG in the common transport directory. All other R/3 Systems connected to this transport directory read the file DOMAIN.CFG during STMS initialization to identify the domain controller and transport group address. If your R/3 Systems do not have a common transport directory, you can manually configure TMS with the address of the domain controller.

When an R/3 System has been configured for the TMS and accepted in the domain, you will find a newly created user TMSADM and generated RFC destinations required for the TMS n When configuring the TMS on an R/3 System, you can specify the application server to be used for all TMS functions. Choose the application server with the highest availability. This is generally the server that provides the enqueue service.
 Transport Domain Management
To check the current status of the transport domain configuration for each R/3 System in the transport domain, access the TMS overview. From the TMS initial screen, choose Overview ® Systems. In this overview, you can also see whether the configuration is up-to-date, and whether any errors occurred when distributing the configuration.

If the R/3 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 domain controller to another R/3 System. In such   case, you must activate the backup controller. Now, the backup controller becomes the domain controller and vice versa.

All planned R/3 Systems are not normally set up at the same time. Instead, the system infrastructure is set up in stages. After setting up the development system and initializing the TMS, you can use the TMS to model the proposed transport routes for the anticipated system infrastructure. The TMS allows you to configure these planned R/3 Systems as virtual systems of the transport domain.
Configuring the Transport Control Program tp

The transport control program tp requires a transport profile that contains information about establishing the database connection for all R/3 Systems in the transport domain. TMS generates and manages this transport profile as a part of the transport domain  configuration. You do not have to adjust the transport profile using a text editor on operating system level.To display the tp parameters of an R/3 System, call Transaction STMS. Choose Overview ® Systems. Mark one system and choose SAP System ® Display. Choose the tab Transport tool.

From the menu, choose Goto ® tp parameters. This displays the parameters in TP_.PFL and the default value of all parameters used by the programs tp and R3trans. If a parameter is not specified, a default value will be used. Global parameters override defaults. Local parameters override global parameters. For example, you can specify a global parameter value for all but one system if a local parameter applies to that system.

To save you the effort of specifying individual transport routes, you can configure standard system groups. Transport routes for the standard system groups are generated automatically. You can choose from the following standard system groups:
ŸSingle system
ŸDevelopment system and production system
ŸDevelopment system, quality assurance system, and production system
If you use the standard configuration function, the current configurations for all R/3 Systems are replaced by the standard settings. Existing development classes, transport layers, or objects created in the R/3 System are not deleted.For complex system groups, define additional consolidation and delivery routes after setting up the standard transport route configuration on the basis of one of the standard system groups. If you modify and save an active configuration, the version counter increases. To activate a stored version, from the R/3 initial screen choose STMS ® Overview ® Transport Routes ® Configuration ® Get other version. 
 Transport Routes
A transport routes can be either a consolidation route or a delivery route. For a standard three-system landscape, the transport routes are as follows:

ŸA consolidation route connects the development system and the quality assurance system. This transport layer is named Z, where is the system ID of the development system. A delivery route is created between the quality assurance system and the production system.In the development system, if changes are made to objects whose development class refers to the (standard) transport layer corresponding to a consolidation route, these changes are recorded in requests and transported to the quality assurance system and then to the production system.

If you change SAP objects, these changes are recorded in repairs, which can be transported in the same way but using the consolidation route "SAP".To create a consolidation route, enter a transport layer name in the field Transport layer. A transport layer name must be within the customer's name range. You can only create delivery routes for consolidation routes that already exist.
Graphical Editor

SAP provides two editors for configuring additional transport routes for more complex system landscapes:

ŸHierarchical list editor : The R/3 Systems in the transport domain and their transport routes are displayed in a tree structure.
Ÿ Graphical editor : The R/3 Systems and their transport routes are displayed graphically. The R/3 Systems can be positioned and linked using the mouse. To call the graphical list editor, use Transaction code STMS. Then, choose Overview ® Transport routes.

To create transport routes, use the mouse to drag the appropriate R/3 Systems from the node area, and drop them in the display area. To create a transport route between these R/3 Systems, from the screen Display Transport Routes, choose Configuration ® Transport Route ® Create Transport Route. The mouse pointer becomes a stylus. Using the stylus, draw a line connecting the two R/3 Systems between which a transport route is desired. In the dialog box Create Transport Route , enter the required information for either the consolidation or delivery route. Save.
 Distribution and Activation of Transport Routes
The TMS checks the following configuration issues:Ÿ Whether the settings of the transport control program tp are consistent with the transport route configuration.Ÿ Whether the deliveries go out from at least one consolidation system Ÿ Whether the transport profile parameter multi level delivery is switched on when using multilevel deliveries for the R/3 Systems involved (< Release 4.0A). Whether the R/3 Systems involved are at least R/3 Release 4.5A when using enhanced transport control and whether the accompanying transport profile parameter “CTC = 1”. The systems also checks if enhanced transport control is mixed with simple transport control. Which effects the configuration has on open tasks and requests. If the configuration of the transport routes is consistent, it is compared with open requests. You cannot release inconsistent requests. 
TMS Authorization Concept
Perform the initial configuration of the TMS on each R/3 System using client 000 and user authorization S_CTS_ADMIN.
To prevent unauthorized access to an R/3 System through the TMS:The TMS authorization check is always performed in the target system. RFC destinations are generated during setup and cannot be modified.Ÿ An R/3 System outside the transport domain may not access R/3 Systems in the transport domain.

For TMS communication, RFC destinations are generated per target system:Ÿ TMSADM@. For this link, the system creates in each R/3 System the user TMSADM, who receives very limited authorizations. This link is used for all read access and for distribution of R/3 System information.The destination for critical access is calculated at runtime based on the address information stored within the TMS configuration when an R/3 system is accepted in the domain. accesses. If the authorizations of TMSADM is not sufficient, the internal connection automatically triggers a logon screen in the target system on which a user with greater authorizations has to identify through logon. If this procedure is too time-consuming, e.g. in case of a large number of R/3 Systems, you may provide user TMSADM with the required authorizations, that is profile S_A.TMSCFG. If an R/3 System is accessed, in which user TMSADM has greater authorizations, the logon procedure is suppressed.

Related Posts

SAP Business  Information warehouse overview