Initial Tms Configuration After Installation: Type Area Topic Author

Type Area Topic Author
Handbook Document SAP Basis Initial TMS Configuration After Installation Huseyin Bilgen
INITIAL TMS CONFIGURATION AFTER INSTALLATION

After SAP R/3 System Installation, you have to configure Transport Management System ( TMS ) for the following reasons: To Create Development Classes. To Create Transportable Requests. To import Transport Requests. To Setup Global Trasnport System between R/3 Systems in your Landscape. To Transport Clients between R/3 system. If your TMS Configuration is inconsistent, you may not be able to create Transportable Requests. You can create requests like Local Change Requests. This means, although your requests type Customizing or Workbench, you will not be able to release them to produce Data and Cofile files. You will only release object locks and no transport will be possible to other systems. As tp program is not configured automatically after Installation, you will not be able to import requests to your system. To overcome those problems, follow the instructions below:
BRIEF EXPLANATIONS OF tp, R3trans and TPPARAM

I. Transport Control Program tp The transport control program tp is a utility for controlling transports between SAP Systems and for upgrading SAP Releases. As a control program, tp uses some special programs that are required to perform complete transports. The transport control program tp is normally called by other programs: Change and Transport System (CTS) Transport Management System (TMS) Upgrade control program R3up tp is currently available for the following operating and database systems: Operating systems: UNIX, Windows NT, AS/400 Database systems: Oracle, Informix, SAP DB, Microsoft SQL Server, DB2/400, DB2 Universal Database, DB2 for OS/390
tp supports a transport network between UNIX and Windows NT systems. II. The R3trans Program
The SAP transport program R3trans is used to transport data between SAP Systems and for the migration between different SAP releases. However, note that R3trans is usually called from other programs, in particular from tp ( Transport Control Program ) and R3up ( upgrade control program ). Therefore, direct use of R3trans is only necessary in exceptions and is not supported other than in these cases. This R3trans documentation does not describe the normal transport procedure, but offers help in cases where the regular tools and methods are insufficient. For example: Exporting and Importing large Clients via direct use of R3trans is an exceptional case. III. Transport Profile ( TPPARAM, TP_<domain>.PFL )
The transport profile is a global parameter file for the program tp and is administrated by the SAP System using the Transport Management System (TMS).
All Rights Reserved. Copyright 2001-2002.
Page 1 of 10
The profile is in the transport directory bin . The profile name corresponds to the convention TP_<domain>.PFL , where <domain> is the name of the transport domain configured in TMS. (You can find the domain in the initial screen of Transaction STMS.) The transport profile contains the following information: Databases from various target systems Parameters describing the frequency of the transport Additional information for system maintenance Every line in a transport profile that is not preceded by a # contains a parameter definition. The various parameters in the transport profile have the following validity: Global (for all SAP Systems in your network) Local (only for one SAP System) Operating system-dependent database-dependent If a parameter does not have a specified value, the SAP System uses the default value. Global parameters override defaults. Local parameters override global parameters. You can therefore specify a parameter value for all but one SAP System and a different value for one special system. Parameters that you specify with the option -D (command line call) deactivate parameters of the transport profile
CONFIGURATION OF A SINGLE SYSTEM LANDSCAPE

If you have a single system in your SAP System Landscape, you have to follow instructions under this section. This will let you to configure single system to act as a Domain controller. If you are going to add your new system to an existing Domain, see INCLUDING SYSTEMS TO A DOMAIN.
PROCEDURE
1. After installation of SAP System, first check whether TPPARAM file exist under /usr/sap/trans/bin. If file doesnt exist you have to create one. a. NT SYSTEMS: There is a template file under /usr/sap/<SID>/SYS/exe/run/ named TPPARAM.NT.Copy this file into /usr/sap/trans/bin/ and rename to TPPARAM ( Figure 1 ).
Figure 1 b. UNIX SYSTEMS: Copy from another SAP System. If you dont have one, Download from our site. TPPARAM file is platform independent, so you can copy from any OS. Just after copy, you have to configure it to match your systems configuration.
Page 2 of 10
2. If file exists, check information in it. You will see some lines like below: <SID>/DBHOST <SID>/DBNAME <SID>/DBTYPE = <dbhost> = <SID> = <db type>
Those lines must contain your system info. <SID> : your system ID. <dbhost> : your central instance host name. <db type> : your database type ( ora, mss, db6, .. ) If informations are wrong, or empty you have to edit them using VI under Unix Systems, or SAPPAD under NT Systems. Try not use Notepad or Wordpad while editing SAP Profile Files. Either use SAPPAD. Because Notepad or Wordpad puts # character in empty places or at the end of lines. You see lines in Notepad like; <SID>/dbtype = ora But in fact SAP reads or sees line as; <SID>/dbtype#=#ora# So couldnt read files. >> To check how SAP Reads files, use AL11 transaction and jump to /usr/sap/trans/bin directory and view file. >> Also check /usr/sap/<SID>/SYS/profile/ directory files. Following is a sample file TPPARAM with minimum configuration options. You have to change accoding to your system info and put under /bin/ directory.
SAMPLE TPPARAM FILE ( SID:HIT, CI_HOST: dwhankt, DB: DB2 ) TRANSDIR = /usr/sap/trans HIT/DBHOST = dwhankt HIT/DBNAME = HIT HIT/DBTYPE = db6 HIT/NBUFFORM =1 HIT/TP_VERSION = 266
After this, you can check whether configuration is ok with following commands: # su - hitadm dwhankt:hitadm>cd /usr/sap/trans/bin dwhankt:hitadm> tp connect HIT
This is tp version 305.12.26 (release 46D) for ANY database Connection to Database of HIT was successful. This is R3trans version 6.05 (release 46D - 28.03.01 - 11:30:00). R3trans finished (0000). tp finished with return code: 0 meaning: Everything OK
dwhankt:hitadm> 3. After configuring TP Profile, you can now configure TMS via SAPGUI. Call transaction STMS in client 000. 4. Following message will appear.
Page 3 of 10
Figure 2 When you confirm the pop-up, following configuration pop-up screen will appear.
Figure 3 This screen creates a new domain named DOMAIN_<SID>. Enter the name and a short description of the transport domain here. Use This Screen, if: this is your only system this is your first system This system will be Domain Controller Save your entries. The following actions are performed automatically in your SAP System: o o o o o The user TMSADM is created. The RFC destinations required for the TMS are generated. The TMS configuration is stored in the transport directory. The transport profile for the transport control program tp is generated. The SAP System is configured as a Single System.
The configuration of the transport domain is now complete for this SAP System. The initial screen of Transaction STMS shows that this SAP System is now functioning as the domain controller of the transport domain ( Figure 4 ).
Page 4 of 10
Figure 4 5. To transport requests from / to this system, you have to specify a Virtual System and Create a Transport Route between Virtual System and Actual System. From STMS main screen, follow Overview Systems ( SHIFT+F6 ) You will see only current system.
Figure 5 6. Execute SAP System Create Virtual System
Figure 6 Now you will see both system under System Overview Screen ( Figure 7 ).
Page 5 of 10
Figure 7 7. Create a Transport Route via Enviroment Transport Routes Transport Routes will let you draw a transport path between systems. A system without a Transport Route cannot export Transport Requests. For example, if you setup a transport route from Development System to Production System, you can sure that only Development System can export transport requests and export from Production System is impossible. Transport Routes will let you draw a transport path between systems. A system without a Transport Route cannot export Transport Requests. For example, if you setup a transport route from Development System to Production System, you can sure that only Development System can export transport requests and export from Production System is impossible. There are 2 ways to setup Transport Routes: Graphical Editor Hierarchical List Editor ( My Favorite Tool ) To change Editor follow Settings Transport Route Editor ( while using List editor Goto Graphical editor ) menu path. Here I will explain procedure with Hierarchical List Editor.
Figure 8 You will see only defined systems in initial screen. 8. To create a Transport Route switch to Editing Mode. If you are new to SAP R/3, choose; Configuration Standart Configuration Development and Production System ( Figure 9 )
Page 6 of 10
Figure 9 Save your changes. Now you will see new but unsaved Transport Route ( Figure 10 ) Configuration.
Figure 10 Transport Layers ZHIT and SAP will automatically created by system if you use Standart Configuration Tool. 9. Save you changes via Save button. Give a short description in pop-up screen ( Figure 11 ).
Figure 11 10. Distribute and Activate Configuration by pressing Yes button in following popup menu (Figure 12)
Page 7 of 10
Figure 12 Now you have completed TMS Configuration of a Single SAP System after Installation.
ADDING A NEW SYSTEM TO AN EXISTING TRANSPORT DOMAIN

Once you have configured an SAP System as the transport domain controller, you can include all additional systems in the transport domain.
PROCEDURE
This occurs in two steps: 1. Submit the new SAP System to be included in the transport domain. 2. Confirm the inclusion in the transport domain controller.
Submitting a System to Be Included

Example: System HKS: This System will be included in Transport Domain DOMAIN_HIT System HIT : This System is the Domain Controller.
To include an SAP System in the transport domain: 1. Log on in client 000 in the SAP System that you want to include in the transport domain (HKS). 2. Call Transaction STMS. 3. The dialog box TMS: Configure Transport Domain appears. (This dialog box only appears if you have not yet configured a transport domain.) 4. Choose Other configuration Include system in domain ( F6 ).
5. In the next dialog box, enter the target host and the system number of the transport domain controller ( Figure 13 ).
Figure 13
Page 8 of 10
6. To find the address data you need to enter here: Log on to the SAP System that functions as the transport domain controller. In the initial screen of the Transport Management System, choose Overview Systems. 7. The system overview appears. 8. c) Position the cursor on the domain controller and choose SAP System Display. 9. The screen Display TMS Configuration: System <SID> appears with the address data you need.
Figure 14 10. If your SAP System consists of multiple application servers, you can choose one server for the TMS. 6. Save your entries. Your SAP System performs the following actions: o o o o Creates the user TMSADM. Generates the RFC destinations required for the TMS Sends the address data to the domain controller Sends the profile parameter for configuring the transport control program to the domain controller Configures the SAP System as a single system
The initial screen of Transaction STMS indicates that the system is waiting for inclusion in the transport domain.
Figure 15
Page 9 of 10
For security reasons, the domain controller must confirm the inclusion of the SAP System. To confirm the inclusion of the system in the transport domain: 1. Log on to the SAP System that functions as the transport domain controller ( HIT ). 2. Call Transaction STMS. 3. Choose Overview Systems. The system overview appears. The column Status shows that an SAP System is waiting to be included in the transport domain.
Figure 16 4. Position the cursor on this SAP System and choose SAP System 5. Confirm the prompt and distribute the configuration. This SAP System now contains the necessary information about all the other SAP Systems in the transport domain. At the same time, the address data of the new SAP System is sent to all the other SAP Systems, and the SAP System is entered in the transport profile of the transport control program. 6. To reject the inclusion of an SAP System in the transport domain, choose SAP System Delete in the system overview of the domain controller. After you have included the first SAP System from another 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 SAP Systems connected to this transport directory automatically propose that the SAP System is included in this transport domain. Approve.
Page 10 of 10

Initial Tms Configuration After Installation: Type Area Topic Author

Uploaded by

Copyright:

Available Formats

Initial Tms Configuration After Installation: Type Area Topic Author

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

Initial Tms Configuration After Installation: Type Area Topic Author

Uploaded by

Copyright:

Available Formats

Type Area Topic Author