The transport domain contains all R/3 Systems whose transports are to be administered together. First, you need to decide which of these R/3 Systems is to be configured as the transport domain controller.
All activities relevant to the entire transport domain, such as configuring transport routes or RFC connections, can only be carried out on the domain controller. SAP therefore recommends configuring the domain controller on an R/3 System with the following characteristics:
High availability
High security precautions
High maintenance level
The domain controller should normally be configured on a production system or quality assurance system.
The resulting system load for the R/3 System configured as the domain controller of a transport domain is low. The load on the domain controller only increases for a short period when the TMS configuration is changed.
Configuring the Transport Domain Controller
Procedure
To configure a system as the transport domain controller, proceed as follows:
Log onto client 000 in the R/3 System which you want to configure as the transport domain controller.
Call transaction STMS.
Sie gelangen in das Dialogfenster TMS: Configure Transport Domain is displayed.
Enter the name and a short description of the transport domain.
The name of the transport domain may not contain blanks. The name of the transport domain may not be changed afterwards without reconfiguring the domain controller.
If your R/3 System consists of several application servers, you can choose a server for the TMS.
Save your entries.
The following actions are performed in your R/3 System:
User TMSADM is created.
The RFC destinations required for the TMS are generated.
The TMS configuration is stored in the transport directory.
Result
The configuration of the transport domain is now complete for this R/3 System. The initial screen of transaction STMS shows that this system is now used as the domain controller of the transport domain.
Including R/3 Systems in the Transport Domain
Prerequisites
Once you have configured an R/3 System as the transport domain controller, you can include all the other systems in the transport domain.
You can do this in two steps:
Apply for inclusion in the transport domain
Confirm inclusion with the transport domain controller
Procedure
To include an R/3 System in the transport domain, proceed as follows:
Log on in client 000 in the R/3 System which you want to include in the transport domain.
Call transaction STMS.
If your systems have a common transport directory, TMS automatically proposes that you include this R/3 System in the transport domain when you call the transaction.
The TMS: Include System in Transport Domain appears, displaying the name of the transport domain and the address data of the domain controller.
If your R/3 System consists of several application servers, you can choose a server for the TMS.
Save your entries.
The following actions are performed on your R/3 System:
User TMSADM is created.
The RFC destinations required for the TMS are generated.
The address data is sent to the domain controller.
The initial screen of transaction STMS indicates that the system is waiting for inclusion in the transport domain.
For safety reasons, the domain controller must confirm inclusion of the R/3 System.
To confirm inclusion of the system in the transport domain, proceed as follows:
Log onto the R/3 System used as the domain controller.
Call transaction STMS.
Choose Overview ® Systems.
This takes you to the system overview.
The Status column shows that an R/3 System is waiting to be included in the transport domain.
Position the cursor on this R/3 System and choose R/3 System ® Accept.
Confirm the prompt and distribute the configuration.
This R/3 System now contains the necessary information about all the other R/3 Systems of the transport domain. The address data of the new R/3 System is also sent to all the other R/3 Systems.
To reject the inclusion of an R/3 System in the transport domain, choose R/3 System ® Delete in the system overview of the domain controller.
Result
The configuration of the transport domain is now complete for this R/3 System.
R/3 Systems without Common Transport Directory
Procedure
If you want to include an R/3 System in the transport domain which does not have the same transport directory as the domain controller, then proceed as follows:
Log on in client 000 in the R/3 System which you want to include in the transport domain.
Call transaction STMS.
The TMS: Configure Transport Domain dialog box is displayed.
Choose Other configuration ® Include system in domain.
In the dialog box displayed, enter the target machine and the system number of the transport domain controller.
You can find the address data to be entered here as follows:
Log onto the R/3 System serving as the domain controller.
In the initial screen of the Transport Management System, choose Overview ® Systems.
This takes you to the system overview.
Position the cursor on the domain controller and choose R/3 System ® Display.
This takes you to the screen Display TMS Configuration: System
If your R/3 System consists of several application servers, you can choose a server for the TMS.
Save your entries.
The following actions are performed on your R/3 System:
User TMSADM is created.
The RFC destinations required for the TMS are generated.
– The address data is sent to the domain controller.
On the initial screen of transaction STMS, you can now see that the system is waiting to be included in the transport domain.
For safety reasons, the domain controller must confirm inclusion of the R/3 System.
To confirm inclusion of the system in the transport domain, proceed as follows:
Log onto the R/3 System used as the domain controller.
Call transaction STMS.
Choose Overview ® Systems.
This takes you to the system overview.
The Status column shows that an R/3 System is waiting to be included in the transport domain.
Position the cursor on this R/3 System and choose R/3 System ® Accept.
Confirm the prompt and distribute the configuration.
This R/3 System now contains the necessary information about all the other R/3 Systems of the transport domain. The address data of the new R/3 System is also sent to all the other R/3 Systems.
To reject the inclusion of an R/3 System in the transport domain, choose R/3 System ® Delete in the system overview of the domain controller.
Result
The configuration of the transport domain is now complete for this R/3 System.
After you have included the first R/3 System from a transport group in the transport domain, the description of the transport domain is also stored in this transport directory. When STMS is first called, all other R/3 Systems connected to this transport directory automatically propose that the R/3 System is included in this transport domain.
Configuring Virtual R/3 Systems
Prerequisites
Once you have planned your system infrastructure, you will generally not install all planned R/3 Systems at the same time. So that you can, however, already model the transport routes of your entire system infrastructure using the TMS, the TMS allows you to configure these R/3 Systems as virtual systems of the transport domain.
Most of the TMS display functions are already available for virtual systems.
You can also configure R/3 Systems that do not yet have maintenance level 3.1G as virtual systems. After a system has been upgraded to Release 3.1G (or higher), you can delete the virtual system from the transport domain and then include an installed R/3 System in the transport domain.
Procedure
To configure a virtual system, proceed as follows:
Log onto the R/3 System acting as the domain controller.
Call transaction STMS.
Choose Overview ® Systems.
This takes you to the system overview.
Choose R/3 System ® Create ® Virtual system.
The TMS: Configure virtual system dialog box is displayed.
Enter the name and a short description of the R/3 System.
The domain controller is proposed as the communications system.
Save your entries and confirm the prompt as to whether the configuration change should be distributed.
A virtual system must also be entered in the configuration file TPPARAM (see: Configuring the Transport Control Program tp).
No comments:
Post a Comment