Configuring the Transport Domain Controller
Prerequisites
You have decided which system should be the Transport Domain Controller.
Procedure
To configure a system as the transport domain controller (and thereby configure a new transport
domain):
1. Log on in client 000 in the SAP System that you want to configure as the transport domain
controller.
2. Enter Transaction STMS. The dialog box TMS: Configure Transport Domain appears.
(This dialog box only appears if you have not yet configured a transport domain.)
3. Enter the name and a short description of the transport domain.
The name of the transport domain may not contain blank characters. You cannot
change the name of the transport domain afterwards without reconfiguring the
domain controller and thereby the entire transport domain.
4. If your SAP System consists of multiple application servers
, you can choose one
server for the TMS.
5. Save your entries. The following actions are performed automatically in your SAP System:
_ 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 [Ext.].
Result
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.
Including SAP Systems in the Transport Domain
Prerequisites
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
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.
2. Call Transaction STMS.
If your SAP Systems have a common transport directory, TMS proposes that you include
this SAP System in the transport domain when you call the transaction.
(If your SAP Systems do not have a common transport directory, see SAP Systems
Without a Common Transport Directory )
The dialog box TMS: Include System in Transport Domain appears, displaying the
transport domain name and the address data of the domain controller.
If your SAP System consists of multiple application servers, you can choose
one server for the TMS.
3. Save your entries. Your SAP System performs the following actions automatically:
_ 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 [Ext.]
The initial screen of Transaction STMS indicates that the system is waiting to be included in the
transport domain.
For security reasons, the domain controller must confirm the inclusion of the SAP
System.
Confirming the Inclusion of the System
To confirm inclusion of the system in the transport domain:
Log on to the SAP System that functions as the transport domain controller.
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.
4. Position the cursor on this SAP System and choose SAP System _ Approve.
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.
To avoid losing data, always check the transport groups after you include
an SAP System in a transport domain.
To reject the inclusion of an SAP System in the transport domain, choose SAP
System _ Delete in the system overview of the domain controller.
Check the consistency of the transport groups. Incorrectly configured
transport groups can damage import queues and transport logs.
Result
The configuration of the transport domain is now complete for this SAP System.
SAP Systems Without a Common Transport Directory
Procedure
To include an SAP System in the transport domain when the system does not have the same
transport directory as the domain controller:
1. Log on in client 000 in the SAP System that you want to include in the transport domain.
2. Call Transaction STMS.
The dialog box TMS: Configure Transport Domain appears.
(This dialog box only appears if you have not yet configured a transport domain.)
3. Choose Other configuration _ Include system in domain.
4. In the next dialog box, enter the target host and the system number of the transport domain
controller.
To find the address data you need to enter here:
a) Log on to the SAP System that functions as the transport domain controller.
b) In the initial screen of the Transport Management System, choose Overview _ Systems.
The system overview appears.
c) Position the cursor on the domain controller and choose SAP System _ Display.
The screen Display TMS Configuration: System <SID> appears with the address
data you need.
5. 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:
_ 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.
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.
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.
4. Position the cursor on this SAP System and choose SAP System _ Approve.
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.
To reject the inclusion of an SAP System in the transport domain, choose SAP
System _ Delete in the system overview of the domain controller.
Check the consistency of the transport groups. Incorrectly configured
transport groups can damage import queues and transport logs.
Result
The configuration of the transport domain is now complete for this SAP System.
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.
Configuring Virtual SAP Systems
Prerequisites
You may not want to install all the SAP Systems you have planned for your system landscape at
the same time. However, you can use TMS to configure SAP Systems as virtual systems in the
transport domain so that you can model the transport routes of your whole system landscape.
Most of the TMS display functions can be used for virtual systems.
You can also configure SAP Systems as virtual systems that do not yet have
Release 3.1G. After you have upgraded the system to Release 3.1G (or higher) you
can replace the virtual system with an installed SAP System.
Procedure
To configure a virtual system:
1. Log on to the SAP system that functions as the transport domain controller.
2. Call Transaction STMS.
3. Choose Overview _ Systems.
The system overview appears.
4. Choose SAP System _ Create _ Virtual system.
The dialog box TMS: Configure Virtual System appears.
5. Enter the name and a short description of the SAP System.
The domain controller is proposed as the communications system.
The communications system is required to act as a substitute for accessing the
transport directory.
6. Save your entries and confirm that you want to distribute the configuration change to all real
SAP Systems.
SAP
Configuring External SAP Systems
Prerequisites
External systems [Ext.] are a special form of virtual systems. A real SAP System is used in their
place to perform actions on the transport directory. They are different from virtual systems in that
they have their own transport directory that you can freely choose.
You can use external systems to:
_ Write transport requests to exchangeable data media
_ Read transport requests from exchangeable data media
_ Send transports to other transport domains using an intermediate directory
_ Send transports to other transport domains using an intermediate directory
If you want to transport between systems in different domains, we recommend that
you link domains with domain links.
Procedure
To configure an external system:
1. Log on to the SAP system functioning as the transport domain controller.
2. Call Transaction STMS.
3. Choose Overview _ Systems.
The system overview appears.
4. Choose SAP System _ Create _ External system.
The screen TMS: Configure External System appears.
5. Enter the path and a short description of the transport directory.
Enter the transport directory path for the specific platform and relative to the
communications system. The transport domain controller is proposed as the
communications system.
6. Save your entries and confirm the distribution prompt.
Configuring the Transport Control Program tp
Use
The transport control program requires a transport profile that contains information about
establishing the database connection for all SAP 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 operating system functions.
If you want to include an SAP System in the transport domain with an SAP version
that is lower than Release 4.5A, you must enter the necessary profile parameters for
this SAP System in the transport profile TPPARAM using a text editor. For more
information on maintaining the file TPPARAM in Releases lower than 4.5A, refer to
the SAP System under R/3 Library _ BC - Basis Components _ Change and
Transport System _ Transport Control _ Transport Control Program tp _ Global
Parameter File.
Configuring Transport Control Program Afterwards
Prerequisites
If the transport domain controller was already configured before upgrading to Release 4.5A,
you can also configure the transport control program afterwards.
The SAP System functioning as the domain controller must have at least Release 4.5A.
The new transport profile generated by TMS is used for all calls of the transport
control program from the SAP System. The settings in the transport profile
TPPARAM are ignored.
To copy the settings from the transport profile TPPARAM to the new configuration, see Copying
Parameters from TPPARAM.
If you also work on the operating system level with the transport control program, see
Transport Control Program tp .
Procedure
To configure the transport control program:
1. Log onto the SAP System functioning as the transport domain controller.
2. Enter Transaction STMS.
3. Choose Overview _ Systems. The system overview appears.
4. Position the cursor on the domain controller.
5. Choose SAP System _ Change. The screen Change TMS Configuration: System <System
name> appears.
6. Choose the tab Transport tool.
7. Choose Extras _ Configure Transport tool.
8. Confirm the prompt and distribute the configuration.
You can then configure the transport control program for all further SAP Systems in your
transport domain as of Release 4.5 (or higher). To do this, proceed as described in Resetting
Parameters to Default Values.
Result
The configuration for the transport control program was determined using the settings in the
instance profile, and a transport profile was generated.
Maintaining and Monitoring the Transport Domain
Once you have configured the transport domain controller and included your SAP Systems in the
transport domain, there will be situations in which the configuration of the transport domain has to
be adjusted.
You must change the configuration, for example when:
_ An SAP System moves to another host
_ A virtual system is replaced with a real system
_ An SAP System is deleted from the transport domain
_ An SAP System is linked to another transport directory
_ Transport domains are linked
_ The settings for the transport control program have to be changed
If the TMS configuration is inconsistent, a warning is displayed on the TMS initial
screen on the domain controller.
The configuration of the transport domain can be changed in the domain controller.
The TMS system overview also provides a number of testing tools in addition to the maintenance
functions. You can use them to check whether the TMS configuration is consistent.
Information in the System Overview
In the TMS system overview (Transaction STMS _ Overview _ Systems), the current status of
the transport domain configuration is shown for each SAP System in the transport domain.
The following system types exist:
Domain controller
Backup domain controller
Virtual system
External system
Controller of another domain
An SAP System can have one of the following statuses:
System is active
System is locked
System was deleted
System waiting for inclusion in the transport domain
System was not included in the transport domain
Communication system is locked
Communication system was deleted
Domain link requested
Waiting for domain link
Transport
Information in the System Overview
22 April 2001
Besides the configuration status, the overview shows if the configuration is up-to-date and if any
errors occurred when distributing the configuration.
TMS configuration is up-to-date
TMS configuration must be adjusted
RFC destinations were not generated
Backup controller has not been completely activated
Status of a system in another domain cannot be shown
New configuration from another domain
To make the system overview more legible, light and dark entries are shown
alternately
Explaining Status Information
System is active
The Transport Management System is configured and ready for use with this SAP System.
The SAP System is an ‘active’ member of the transport domain. For an active SAP System, you
can configure transport routes and perform transports using TMS from the
transport domain controller.
System is locked
The Transport Management System is locked for this SAP System.
The TMS transport function is deactivated for this SAP System, and the transport domain
controller can distribute transport route configurations to this SAP System.
You can lock and unlock SAP Systems from the transport domain controller.
System was deleted
An SAP System was deleted from the transport domain.
You can use TMS to block transports from being performed for this SAP System. The transport
route configuration in the transport domain controller cannot be changed anymore for this SAP
System.
If you restart Transaction STMS in this SAP System, you can resubmit to be included in the
transport domain.
System waiting for inclusion in the transport domain
The SAP System submitted to be included in the transport domain in the transport domain
controller.
The TMS transport functions are still deactivated. To activate the TMS for this SAP System, you
must confirm the inclusion in the transport domain in the domain controller.
System was not included in the transport domain
The administrator rejected the inclusion in the transport domain of this SAP System in the
transport domain controller.
If you restart Transaction STMS in this SAP System, you can resubmit to be included in the
transport domain.
Communication system is locked
The communication system is locked for this virtual SAP System.
If the accompanying communication system is locked because all accesses to a virtual R/3
System occur using the communication system, the virtual SAP Systems are automatically
locked. If you unlock the communication system again, all the other relevant virtual SAP Systems
are also unlocked.
Communication system was deleted
The communication system is locked for this virtual SAP System.
Domain link requested
You have requested to link to another domain in the domain controller of that domain. You must
confirm the link between the domains in this controller so that the SAP Systems in the two
domains can communicate.
Waiting for domain link
A domain controller in another domain has requested a link to this domain. Confirm this link to
enable all SAP Systems in the two domains to communicate with each other. You can now make
transports between systems in two different domains.
TMS configuration is up-to-date
The transport domain configuration for this SAP System is identical to the reference configuration
on the transport domain controller.
RFC destinations were generated.
This status information is only relevant in the domain controller.
TMS configuration must be adjusted
The transport domain configuration for this SAP System does not match the reference
configuration in the transport domain controller.
The reasons for this may be that:
_ You changed the TMS configuration on the domain controller but did not distribute it.
Information in the System Overview
24 April 2001
_ When distributing the changed TMS configuration, this SAP System was not available.
In both cases, you must distribute the transport domain configuration again.
This status information is only relevant in the domain controller.
RFC destinations were not generated
When creating the RFC destinations, an error occurred in this SAP System.
You can find the error source in the CCMS Alert Monitor. After eliminating the error,
you can distribute the TMS Configuration again. You can regenerate the RFC
destinations locally in an SAP System from the TMS system overview by choosing Extras _
Generate RFC destinations
If the transport domain configuration was changed, you must distribute it to all SAP
Systems in the transport domain. This recreates the necessary RFC destinations in
all SAP Systems.
Backup controller has not been completely activated
When activating the backup domain controller, errors occurred.
You can find the error source in the CCMS Alert Monitor. After eliminating the error,
you can restart the activation on the new domain controller by distributing the TMS Configuration
.
Status of a system in another domain cannot be shown
You cannot display the status of the TMS configuration for systems in another domain, with the
exception of the domain controller.
New configuration from another domain
The TMS configuration of another domain has been changed. You can now distribute this change
to the systems of the local domain. This is done implicitly when you distribute a change to the
local configuration. You can also distribute changes explicitly
User Settings for the TMS System Overview
In the TMS system overview, you can make the following user-specific settings:
_ System overview display
_ Light/dark alternately
To make the system overview more legible, entries are shown alternately light and
dark.
_ Group by system type
If you choose this setting, the system overview is sorted in the following order:
_ SAP Systems
_ Virtual SAP Systems
_ External SAP Systems
The domain controller is always displayed as the first SAP System in the list.
Otherwise, all SAP Systems are sorted alphabetically.
_ Behavior when changing configuration
_ Distribute automatically after changes
The configuration of the transport domain is distributed immediately after each
change. This setting is useful if your transport domain only consists of a few SAP
Systems.
_ Prompt, if distribution should be immediate
There is a prompt after each configuration change, asking if the changed
configuration should be distributed. This setting is useful, if you manage many SAP
Systems in your transport domain, or you often have to change configurations. This
enables you to decide when you want to distribute the configuration.
_ Do not distribute changes automatically
After a change, the configuration is not automatically distributed and there is no
prompt asking if it should be distributed. Only experienced administrators should use
this setting.
Changing User-Specific Settings
Procedure
To change the settings:
1. Enter Transaction STMS.
2. Choose Overview _ Systems. The system overview appears.
3. Choose Extras _ Personal Settings.
4. Choose the settings you want.
5. Confirm these settings with Enter.
Result
The changed settings for the system overview and the way the configuration is changed have
been stored for your user.
Configuring the Backup Domain Controller
Prerequisites
In your transport domain, the SAP System that is configured as the domain controller is of special
significance. If this SAP System fails, you cannot make changes to the TMS configuration during
this time. Therefore if your transport domain contains more than three SAP Systems, we
recommend configuring a backup domain controller. If your domain controller fails, the backup
controller can assume the function of the domain controller.
The SAP System that you want to use as the backup controller must have the same
release version as the domain controller. Otherwise, configuration information may
be lost when changing the transport domain controller.
Procedure
To configure a backup domain controller:
1. Log onto the SAP System functioning as the transport domain controller.
2. Enter Transaction STMS.
3. Choose Overview _ Systems. The system overview appears.
4. Position the cursor on the domain controller.
5. Choose SAP System _ Change. The brings you to the screen Change TMS Configuration:
System <SID>.
6. In the field Backup, enter the SAP System you want to use as the backup controller of your
transport domain.
7. Save your entries and distribute the configuration change.
Activating the Backup Domain Controller
Prerequisites
If your domain controller failed and you have to make changes to the TMS configuration, you can
activate the backup controller.
Procedure
To activate the backup domain controller:
1. Log on to the SAP System functioning as the backup domain controller.
2. Enter Transaction STMS.
3. Choose Overview _ Systems. The system overview appears.
4. Choose Extras _ Activate backup controller.
5. Confirm the prompt.
Result
The backup domain controller is activated as the transport domain controller. The configuration
change is distributed to all SAP Systems in the transport domain. The status bar indicates SAP
System in which the configuration is being adjusted.
When you have activated the backup domain controller, the "old" domain controller is
automatically made the "new" backup controller, if it can be accessed.
As long as the information that the domain controller has changed cannot be
distributed to all the SAP Systems of the transport domain, the system overview of
the new controller shows that the backup controller activation is still incomplete.
You can only change the transport domain configuration if the backup controller is
completely activated.
Moving the Domain Controller to Another SAP System
Prerequisites
Because the domain controller can only be moved as long as it is functioning, you must always
configure a backup domain controller.
Procedure
To move the domain controller to another SAP System:
1. Configure the SAP System you want to use as the new domain controller as the
backup domain controller.
2. Activate the previous domain controller as the backup domain controller.
Result
The previous domain controller becomes the backup domain controller. The SAP System that
you configured as the backup domain controller becomes the new domain controller.
Locking/Unlocking TMS for an SAP System
Prerequisites
In certain circumstances, you may want to lock an SAP System for TMS accesses. If you have to
stop an SAP System for hardware maintenance, for example, communicate this to the other SAP
Systems in the transport domain. This prevents unnecessary attempts to access an SAP System
that cannot be reached.
Locked SAP Systems are not displayed in the import overview. Display and import functions are
not available for SAP Systems that have been locked.
If an SAP System is locked for the TMS, all virtual SAP Systems that have this SAP
System configured as a communications system are also locked.
Procedure
To lock an SAP System:
1. Log onto the SAP System functioning as the transport domain controller.
2. Enter Transaction STMS.
3. Choose Overview _ Systems. The system overview appears.
4. Position the cursor on the SAP System you want to lock.
5. Choose SAP System _ Lock.
6. Confirm the prompt and distribute the configuration.
The SAP System has been locked for the TMS. All SAP Systems belonging to the transport
domain are informed that the SAP System has been locked.
To unlock a locked SAP System:
1. Log onto the SAP System functioning as the transport domain controller.
2. Enter Transaction STMS.
3. Choose Overview _ Systems. The system overview appears.
4. Position the cursor on the SAP System you want to unlock.
5. Choose SAP System _ Unlock.
6. Confirm the prompt and distribute the configuration.
The SAP System has been unlocked for the TMS. All systems belonging to the transport domain
are informed that the SAP System has been unlocked.
If the TMS configuration of the transport domain has changed in the meantime, this is
communicated to the SAP System that is unlocked.
SAP
Deleting an SAP System from the Transport Domain
Note that the original version of the TMS configuration for the entire transport domain
is destroyed if you perform one of the following actions:
_ Delete the domain controller from the transport domain
_ Delete the TMS configuration of the domain controller for the transport
domain
You can only maintain the transport domain after these actions if you have activated
the backup domain controller.
If you have not configured a backup domain controller, you must delete and then
rebuild the TMS configuration for all systems.
Procedure
Deleting an SAP System from the Transport Domain
If you delete an SAP System from the transport domain, it is also deleted from the
profile of the transport control program. After you have deleted the SAP System, you
cannot release or import transport requests in this system.
To delete an SAP System from the transport domain:
1. Log on to the system functioning as the transport domain controller.
2. Enter Transaction STMS.
3. Choose Overview _ Systems. The system overview appears.
4. Position the cursor on the SAP System you want to delete.
5. Choose SAP System _ Delete.
6. Confirm the prompt and distribute the configuration.
The SAP System is deleted from the TMS configuration. This information is distributed to
the other systems.
If you cannot delete a system on the transport domain controller, you must delete
the TMS configuration of this system.
This is the case, for example, if:
_ A system deleted from the domain that is replaced by a backup imported
later on, functions as member of the domain, although is does not belong to
the domain any longer.
_ The TMS configuration was accidentally deleted on the domain controller
and a backup controller was not configured.
Deleting the TMS Configuration for a System
To delete the TMS configuration for a system:
1. Log on to this SAP System.
2. Enter Transaction STMS.
3. Choose Overview _ Systems. The system overview appears.
4. Choose Extras _ Delete TMS configuration.
5. Confirm the prompt.
The information about deleting the TMS configuration for this system is not
distributed to other systems.
Result
The TMS is deactivated for systems that either were taken out of the transport domain or had the
TMS configuration deleted:
_ The RFC connections generated by TMS are deleted.
_ User TMSADM is not deleted.
_ Transport requests or transport objects are not deleted.
_ The transport route configuration is deactivated, but not deleted. (After TMS is reconfigured,
you can reactivate and distribute the old transport route configuration.)
_ The settings from the transport profile are deleted for systems deleted from the transport
domain. After the deletion in this system, you cannot release or import any transport requests
in this system.
Changing the Configuration of an SAP System
Prerequisites
Once you have included an SAP System in the transport domain, you can change the following
settings on the domain controller at any time:
_ Short description of the transport domain
_ Backup domain controller
_ Short description of the transport group
_ Short description of the SAP System
_ Transport group
_ Host name and system number for the RFC address
_ Communication system
_ Profile parameter for the transport control program tp
Procedure
To change the configuration of an SAP System:
1. Log onto the SAP System functioning as the transport domain controller.
2. Call Transaction STMS.
3. Choose Overview _ Systems. The system overview appears.
4. Position the cursor on the SAP System where you want to change the configuration.
5. Choose SAP System _ Change. The screen Change TMS Configuration: System <SID>
appears where you can make changes.
In the field Description in the upper part of the screen, you can change the short text for
the SAP System. The other parameters are distributed on three tabs.
– The tab Management gives you information about the current configuration status.
– Under the tab Communication, you can change the parameters of the transport
domain, the transport group and the RFC connection of the SAP System.
– Under the tab Transport tool, you can change the parameters for the transport
control program.
The short descriptions of the transport domain, groups, and the SAP Systems are
stored for the specific language. If you change a text, you change this text for the
language in which you have logged on.
6. Save your changes and distribute the configuration changes to all SAP Systems in the
transport domain (see: Distributing the Transport Domain Configuration.
If the host name or the system number of the SAP System functioning as the domain
controller changes, you have to set the new address of the domain
controller on all SAP Systems in the transport domain. Avoid these manual actions
by configuring a backup controller and activating it before you change the
domain controller.
Changing the Domain Controller Address
Prerequisites
If the host name or the system number of the SAP System serving as the domain controller
changes, you have to set the new address of the domain controller on all SAP Systems in the
transport domain.
You can only change the RFC address of the domain controller outside of the
domain controller.
Avoid these manual actions by configuring a backup controller and activating it
before changing the domain controller.
Procedure
To change the address of the domain controller:
1. Log onto the SAP System that you want to inform about the new domain controller address.
2. Enter Transaction STMS.
3. Choose Overview _ Systems. The system overview appears.
4. Position the cursor on the domain controller.
5. Choose SAP System _ Change. The screen Change TMS Configuration: System <SID>
appears.
6. Choose the tab Communication.
7. Choose Configuration _ Display _ Change. The fields Target host and System number are
ready for input.
8. Change the address and save your entries.
Repeat this process for all the other SAP Systems of the transport domain.
Changing Parameters for the Transport Control Program
Procedure
To change the automatically generated profile parameters for the transport control program:
1. Log onto the SAP System functioning as the transport domain controller.
2. Call Transaction STMS.
3. Choose Overview _ Systems. The system overview appears.
4. Position the cursor on the SAP System you want to change.
5. Choose SAP System _ Change. The screen Change TMS Configuration: System <System
name> appears.
6. Choose the tab Transport tool.
First, all the global parameters are displayed and then all the local parameters.
The global parameters are identical for all SAP Systems in the domain.
To change a global parameter to a local parameter, you must delete the global
parameter and enter the new local parameter.
The operating system is only displayed if values exist for this field.
7. Save your entries and distribute the changed configuration.
If you enter a parameter unknown to the transport control program, or a value that is
not permitted, the transport control program ignores this entry in the transport profile.
To ensure that you have entered the correct parameters and values, compare your
entries with the settings actually used by the transport control program. After you
have stored and distributed the configuration, display all the parameters that the
transport control program uses for a specific SAP System (see: Displaying
Parameters for the Transport Control Program.
For information on individual parameters of the transport control program, see Transport Profile
.
Color Legend for tp Parameters
In the parameter display for the transport control program, parameters may be highlighted with a
color, or have an icon in the column Parameter Type.
The color used for the request means the following:
Red Parameter Changed, but not yet Stored
The icons displayed as a parameter type mean the following:
Only for tp calls on the operating system level
Parameter was generated from SAP profile
Generated parameter modified by user
No icon Parameter inserted by user
Color Legend Explanation
Parameter changed, but not yet stored
If you change parameters manually or the TMS changes them for you, all the changes are highlighted in color. The highlighted selection remains until you have stored or rejected the changes.
Only for tp calls on the operating system level
These parameters (for example TRANSDIR) are only relevant if you also use tp on the operating
system level. When you call tp from the SAP System, these parameters are determined from the
profile parameters of the instance at runtime and are overridden.
Parameter was generated from profile
These parameters are derived from the profile parameters of the instance profile when
configuring the transport domain, and are generated by TMS in the transport profile. Therefore, if
you change the configuration of an SAP System, you only have to change parameters such as
the database host name in only one place. You can read these parameters at any time from the
profile and copy them to the transport profile (see Resetting Parameters to Default Values.
Generated parameter modified by user
These parameters were derived by the TMS from the instance profile and generated in the
transport profile. The value of these parameters were changed by the user at a later time.
Parameter inserted by user
These parameters were inserted by the user. TMS cannot not automatically determine and check
these parameters.
Distributing the Transport Domain Configuration
Prerequisites
After a change is made to the transport domain configuration, you must distribute it to all SAP
Systems in the transport domain. Each time you make a change to the domain controller, a
dialog box appears prompting you to distribute the configuration.
You can therefore make several changes to the domain controller and distribute all these
configuration changes after that at one time.
You can set the behavior for configuration changes to be user-specific.
Procedure
To distribute the changed configuration at a later time:
1. Log on to the SAP system that functions as the transport domain controller.
2. Call Transaction STMS.
3. Choose Overview _ Systems. The system overview appears.
4. Choose Extras _ Distribute and activate configuration. The dialog box Distribute and
Activate TMS Configuration appears.
You have the following options:
_ Distribute configuration to all systems
All changes to the configuration are distributed to all systems in the local domain and
activated. The controllers in other domains are informed of the changes to the
configuration.
This includes both changes to the local domain and to other domains.
_ Distribute only to systems without current configuration
The changes to the configuration are distributed to systems whose configuration is
not up-to-date, and then activated. The controllers in other domains are informed of
the changes to the configuration, if this is necessary.
_ Distribute configuration to other domains
This includes the changes from other domains.
The status bar indicates the SAP System in which the configuration is being adjusted.
You cannot distribute the configuration if a controller was not completely relocated
because not all SAP Systems were accessible. The system recommends that you
complete the controller relocation.
Result
_ The configuration of the transport domain was distributed to the SAP Systems according to
the selected options.
_ The RFC connections required by TMS were generated in the SAP Systems.
_ The transport profile for the transport control program was distributed to the transport groups.
Checking the Transport Directory
Prerequisites
The system checks if:
_ All the subdirectories of the transport directory can be accessed
_ Files can be stored in these subdirectories
Procedure
To check the availability of the transport directory:
1. In the system overview, position the cursor on the SAP System where you want to check the
transport directory.
If you did not select an SAP System, the transport directory of all the SAP Systems
in the transport domain are checked.
2. Choose SAP System _ Check _ Transport directory.
The status bar displays the actions that are executed for the check.
Result
A hierarchical list is displayed in which you can see the individual statuses. You can expand the
list down to the individual actions.
If errors are displayed during the check, you must use operating system functions to see why the
transport directory cannot be accessed. Typical sources of errors are missing authorizations for
the processes and network problems.
Checking Transport Groups
Prerequisites
When the transport groups are checked, the system tests whether all SAP Systems within a
transport group have the same transport directory. It also checks if SAP Systems in different
transport groups access different transport directories.
Procedure
To check the transport groups only:
5. Call Transaction STMS.
6. Choose . The system overview appears.
3. Choose Goto _ Transport groups. The screen Display TMS Configuration: Transport
Groups.
4. Choose Configuration _ Check transport groups.
To check the transport directories and the transport groups:
1. Check the transport directories of all SAP Systems in the transport domain.
2. Choose Goto _ Transport groups.
The check involves creating test files for all SAP Systems in the transport domain. A check is
then made on all systems to see which of these test files are readable. The result is compared
with the configuration of the transport domain.
If the check for the transport groups shows that the systems are incorrectly assigned
to the groups, you must adapt the TMS configuration. Then repeat this check.
Remember that incorrectly configured transport groups can damage import queues
and transport logs. You must check the consistency of the transport groups after you
include new systems in the transport domain.
Result
The test result is output in the form of a matrix. The icons used mean the following:
Correct group assignment
Incorrect group assignment
Check could not be performed
TMS in SAP Systems with Multiple Application Servers
Prerequisites
When you configure the TMS in an SAP System for the first time, you can specify the application
server to be used for all TMS functions.
Procedure
To specify the application server:
1. In the dialog box TMS: Configure Transport Domain, or in the dialog box TMS: Include SAP
System in Transport Domain, choose Address.
The address data of your system is displayed. It is used to generate the RFC
connections.
2. In the field Target host, use the F4 help to choose the host name of the application server
you would like to use for the TMS.
Choose the application server with the highest availability. This is generally the
server used for the enqueue process.
3. Choose Continue.
The application server chosen is used for the TMS functions after the TMS configuration.
If the SAP System has already been included in the transport domain, you can still change the
address of the application server at any time.
To change the address of the application server:
1. Log on to the SAP System functioning as the transport domain controller.
2. Enter Transaction STMS.
3. Choose Overview _ Systems. The system overview appears.
4. Position the cursor on the SAP System you want to change.
5. Choose SAP System _ Change.
6. Choose the tab Communication.
7. In the field Target host, enter the host name of the application server.
8. Choose Connection test to check if the machine name entered is correct.
9. Save your entry and distribute the changed TMS configuration.
Configuring Links Between Transport Domains
Use
If you have configured multiple transport domains and want to make transports between systems in different
domains, you can use domain links to link the two domains.
Prerequisites
There must be a permanent network connection between the systems in the two domains, similar
to the connection between systems within the same domain.
The domain controller systems in both domains must have SAP Release 4.6C, or higher.
If you cannot operate a permanent RFC connection between systems in the two
domains, you can use external systems to make transports between the
two.
Functions
_ You can make transports between systems in different domains in the same way as you
make transports between systems in different transport groups; RFC is used to transfer
transport files between the transport directories involved.
_ You can display transport logs of systems in the other domain.
_ You can compare versions of Repository objects in systems in different domains.
_ Domains are independent administrative units. You can only make changes (such as
transport route changes) in the controller of the domain.
_ If you need to administrate a large number of systems (more than 50), it makes sense to split
the systems into domains; place systems which transport to each other frequently in the
same domain. This makes is easier to distribute changes to the configuration, since changes
are distributed more quickly in domains that contain fewer systems.
_ Transport routes are not distributed between domains. You can, however, configure a route
between systems in different domains, but must configure it twice, once in each domain.
_ You can choose to configure the Workflow Engine in each domain, or you can use the
Workflow Engine of a different domain.
Activities
Linking Domains with Domain
Linking Domains with External Systems
Domain Links
Use
If you have configured multiple transport domains and want to make transports between systems in different
domains, you can use domain links to link the two domains.
Prerequisites
There must be a permanent network connection between the systems in the two domains, similar
to the connection between systems within the same domain.
The domain controller systems in both domains must have SAP Release 4.6C, or higher.
Procedure
Linking two domains with a domain link involves two steps:
1. Request a link between two domains.
2. Confirm the link between the two domains.
Requesting a Link Between Two Domains.
To request a link between two transport domains, proceed as follows:
1. Log on to one of the two domain controller systems.
2. Call Transaction STMS.
3. Choose Overview _ Systems. The system overview appears.
4. Choose SAP System _ Create _ Domain link.
The dialog box Request for Linking 2 Domains appears.
5. Enter the system name, host name and system number of the domain controller you want to
link to, and then confirm your entries.
Your SAP System performs the following actions automatically:
_ Generates the required RFC destinations.
_ Sends the address data of the controller to the controller in the other domain.
You can now see that you have requested the domain link to the other domain in the
system overview.
For security reasons, you now need to confirm the link between the two domains in
the other controller.
Confirming a Link Between Two Domains.
To confirm a link between two transport domains, proceed as follows:
1. Log on to the domain controller in the other domain.
Call Transaction STMS.
3. Choose Overview _ Systems. The system overview appears.
4. Position the cursor on the domain controller where you requested the domain link and
choose SAP System _ Approve.
5. Confirm the prompt and distribute the configuration.
The two domain controllers now exchange all necessary information about the systems
in their domains. This information is distributed to all systems in the domain whose
controller you are currently logged on to. A transport profile is generated, which contains
all systems in both domains.
The information about the systems in the other domain is not automatically
distributed to the systems in the domain where you requested the domain link. This
means that you must distribute the new configuration to these systems.
To reject a link between two domains, go to the system overview of the domain
controller and choose SAP System _ Delete.
Result
You have created a domain link between two transport domains. You can now see all systems in
both domains in the system overview and the import overview. You can now make transports
between systems in two different domains.
Remember that you can only display systems with Release 4.6C or higher.
Linking Domains with External Systems
Prerequisites
You can use external systems to make transports between domains.
External systems are like virtual systems. This means that they are accessed using a
communications system. However, for this type of system, an separate transport directory is also
defined. This directory can either reside on a disk partition that can be accessed by an SAP
System in the other domain, or it is on an exchangeable data medium.
Procedure
To transport between two transport domains using an external system, proceed as follows:
1. In both transport domains, define an SAP System that exists as a real system in the other
transport domain as an External System.
2. As the communications system, choose an SAP System that can access the intermediate
directory or the drive of the exchangeable data medium.
3. Define the platform-specific path to this directory as the transport directory for the respective
external system.
You can now route transports to the external system. All necessary files are stored in the
external transport directory.
Using the queue display of the external system, you can check which transport requests
have already been created there.
4. To transfer them to the other domain, you must adjust the import queue in the relevant target
system (see Special Features when Using Multiple Transport Directories once
the transport data has been made accessible.
5. If you have chosen a target system in the source domain that does not exist in the target
domain, you can still transfer the transport requests.
To do this, define another external system in the target domain with the name of the
original target system. From the queue display of this system, you can route the transport
requests to the SAP System you have chosen.
Creating a System List
Use
The import overview can quickly become very complicated if a domain contains a
large number of systems, or if the overview involves multiple domains. A particular user may only
be interested in a certain group of systems (for example, an administrator may only make imports
for certain systems). To help these users, you have the option of reducing the import overview to
a predefined group of systems.
Procedure
To create a system list:
1. Log on to the domain controller.
2. Call Transaction STMS.
3. Choose Overview _ Systems. The system overview appears.
4. Choose Goto _ System lists. The screen Display View "TMS System Lists": Overview
appears.
5. Choose Display _ Change.
6. Choose New entries.
7. Enter the name and a description for the new system list.
8. Select the new entry.
9. On the left of the screen, choose the node Systems/Clients. The screen Change View
"Systems/Clients": Overview appears.
10. Choose New entries.
11. Enter the systems you are interested in and save.
Note that the Client column is not currently used.
12. To exit the screen Change View "Systems/Clients": Overview, choose Table view _ Exit.
13. Distribute the configuration immediately, so that you can use the system list in all your
systems. To do this, go to the system overview and choose Extras _ Distribute and activate
configuration.
You do not need to distribute the configuration if you only want to use the system list
in the controller system. System lists are distributed automatically when you
distribute changes to the TMS configuration.
Result
You have created a system list that you can select in the personal settings in the import overview
.
Deleting the Transport Domain
Use
You can delete a transport domain if:
_ You want to rebuild the transport domain again.
_ The TMS configuration was accidentally deleted on the transport domain controller and a
backup domain controller was not configured.
If you want to delete a transport domain, you must delete the TMS configuration for
all systems in the transport domain.
Prerequisites
Ensure that no objects are transported while you delete the transport domain.
Procedure
To delete the transport domain:
1. On the transport domain controller, delete all systems in the transport domain except for the
domain controller.
2. At the end, delete the transport domain controller.
Result
The TMS is deactivated for systems that had the TMS configuration deleted.
You can now rebuild the transport domain.
Configuring Transport Routes
Prerequisites
Before you can configure the transport routes, the following prerequisites must be met:
_ The transport domain has been configured.
_ All SAP Systems involved were included in the transport domain.
Functions
The configuration of the transport routes is managed in the SAP System that serves as the
transport domain controller, and can be distributed to and activated in all other
connected SAP Systems in the transport domain.
The transport route configuration consists of:
_ System attributes
_ Consolidation routes
_ Delivery routes
_ Target groups
SAP provides two editors for configuring transport routes:
_ Graphical editor
The SAP Systems and their transport routes are displayed graphically.
You can position and link the SAP Systems together by clicking and holding the mouse.
_ Hierarchical list editor
The SAP Systems and their transport routes are displayed in a tree structure.
User Settings for Transport Route Configuration
Prerequisites
To maintain the transport route configuration (Transaction STMS _ Overview _ Transport
routes), you set the editor mode with user-specific settings:
_ Graphical editor
The SAP Systems and their transport routes are displayed graphically.
_ Hierarchical list editor
The SAP Systems and their transport routes are displayed in a tree structure.
Procedure
To change the editor mode:
1. Call Transaction STMS.
2. Choose Extras _ Settings _ Transport routes.
3. Choose the desired setting.
4. Confirm these settings.
Result
The changed settings for the system overview and the behavior for changing configurations have
been stored for your user.
Transport Management System (BC-CTS-TMS) SAP AG
Using the Graphical Editor
64 April 2001
Using the Graphical Editor
Prerequisites
The graphical editor is divided into several areas:
_ Insertable objects
All SAP Systems and target groups not connected via transport routes
_ Display area
Graphical representation of the SAP Systems and target groups with their transport
routes.
_ Navigation area
Positioning on the display area.
Procedure
To configure the transport routes with the graphical editor:
1. Log on in client 000 in the SAP System serving as the transport domain controller.
2. Choose Overview _ Transport routes. The screen Display Transport Routes appears.
3. Choose Goto _ Graphical editor.
4. To switch to change mode, choose Configuration _ Display _ Change.
In your User-Specific Settings, you can set the system so that when you
choose Overview _ Transport routes takes you directly to the graphical editor.
Configuring Standard System Groups
Use
You can configure standard system groups explicitly without specifying the individual transport
routes. Transport routes for standard system groups are generated automatically.
Standard system groups are:
_ Single systems
_ Development and production systems
_ Development, quality assurance, and production systems
If you use the function Standard configuration, all previous configurations for all SAP
Systems are replaced by the default settings.
Default transport layers and transport routes that already exist are deleted.
Transport layers, development classes and objects that already exist are kept.
Configuring Single Systems
Prerequisites
When you configure a single system, no transport routes are created.
This SAP System can only be supplied with special transports.
Procedure
To configure a single system:
If you use the function Standard configuration, all previous configurations for all SAP
Systems are replaced by the default settings.
Default transport layers and transport routes that already exist are deleted.
Transport layers, development classes and objects that already exist are kept.
1. In the graphical editor, choose Configuration _ Standard configuration _ Single system.
In the graphical editor, your single system is displayed under Insertable objects.
2. Save the configuration.
3. To check the single system configuration, choose Configuration _ Check _ Transport
routes.
4. To activate the configuration, choose Configuration _ Distribute.
Result
The single system has been configured.
Configuring the Development and Production Systems
Prerequisites
When you configure a 2-system landscape, you can specify which SAP System is the
development system and which is the production system. The transport route is generated
automatically.
Procedure
To configure the development and production system, proceed as follows:
If you use the function Standard configuration, all previous configurations for all SAP
Systems are replaced by the default settings.
Default transport layers and transport routes that already exist are deleted.
Transport layers, development classes and objects that already exist are kept.
1. In the graphical editor, choose Configuration _ Standard config. _ Development and
Production system.
2. Enter the names of your SAP Systems and choose Continue.
In the Display area of the graphical editor, your SAP Systems and their transport routes are
shown.
3. Save the configuration.
4. To check the transport route configuration, choose Configuration _ Check _ Transport
routes.
5. To distribute the transport route configuration to all SAP Systems involved, choose
Configuration _ Distribute.
When doing so, you must enter your user ID and password in all SAP Systems that you
want to change.
Result
The development and production systems have been configured and are connected to each
other by a transport route (consolidation route).
The transport route configuration was distributed to and activated in all SAP Systems involved.
Configuring the Development, Quality Assurance and
Production Systems
Prerequisites
When you configure a 3-system landscape, you can specify for each SAP System which role it
has in the system group. The transport routes are generated automatically.
Procedure
To configure the transport routes for a development, quality assurance, and production system,
proceed as follows:
If you use the function Standard configuration, all previous configurations for all SAP
Systems are replaced by the default settings.
Default transport layers and transport routes that already exist are deleted.
Transport layers, development classes and objects that already exist are kept.
1. In the graphical editor, choose Configuration _ Standard configuration _ 3 systems in
group.
2. Enter the names of your SAP Systems and choose Continue.
In the Display area of the graphical editor, your SAP Systems and their transport routes are
shown.
3. Save the configuration.
4. To check the transport route configuration, choose Configuration _ Check _ Transport
routes.
5. To distribute the transport route configuration to all SAP Systems involved, choose
Configuration _ Distribute.
When doing so, you must enter your user ID and password in all SAP Systems that you
want to change.
Result
The development, quality assurance, and production system have been configured and are
connected to each other by transport routes (consolidation route, delivery route).
The transport route configuration was distributed to and activated in all SAP Systems involved.
Configuring Complex System Groups
Use
Transport route configurations are referred to as complex if they cannot be categorized according
to one of the following three models:
_ Single System
_ Development and Production System
_ Development, Quality Assurance, and Production System
In complex system groups, the configuration must be created by defining individual consolidation
and delivery routes.
You can also create your transport route configuration on the basis of a Standard
Configuration.
Creating a Transport Route
Prerequisites
In the graphical editor in the area Insertable objects, the SAP Systems and target groups of the
transport domain are listed that are not connected via transport routes.
Before you can create transport routes, you have to drag the SAP Systems to be configured and
the target groups (for extended transport control) using the mouse from the area Insertable
objects and place it in the Display area.
Procedure
To create transport routes:
1. In the Graphical editor, choose Configuration _ Transport route _ Create.
The mouse pointer becomes a pencil icon.
2. Click one SAP System and hold the mouse button.
3. Drag the pencil icon to the SAP System or the target group (for extended transport control)
with which the first SAP System is to be linked, and release the mouse button.
The dialog box Create Transport Route appears.
4. Select Consolidation route or Delivery route.
If you want to create a consolidation route, enter in the field Transport layer a name:
Z<sid> (<sid> - name of the development system)
Transport layers that do not exist are created automatically. Another way to create a
transport layer is to choose Edit _ Transport layer _ Create. The graphical presentation
requires that transport layers can only be seen if they contain a transport route.
5. Choose Continue.
If you choose Consolidation route, enter a short description in the dialog box Create
Transport Layer and choose Copy.
The graphical editor appears, where the created transport route is shown in the display
area.
To create all the necessary transport routes, use this procedure.
6. To stop creating transport routes, click anywhere in the display area.
7. Save the transport configuration.
SAP
Creating and Changing Target Groups
Prerequisites
For extended transport control, you can create target groups that can serve as transport targets
from consolidations and deliveries for simultaneously servicing different SAP Systems and/or
clients.
Procedure
To create target groups:
1. Choose Edit _ Target group _ Create.
The dialog box Create Target Group appears.
2. When you enter the target group use a “/” at the beginning and end of the target group and a
short text.
3. Enter the system/client combination.
4. Copy the target group in the current configuration.
To change the target group:
1. Select the target group.
2. Choose Edit _ Target group _ Change.
The dialog box Change Target Group appears.
3. To insert a new target, choose Insert row.
4. To delete a target, choose Delete row.
5. Copy the target group in the current configuration.
Saving the Transport Route Configuration
Use
All parts of the configuration are saved in such a way that when the editor is accessed again, the
latest edited version is available.
If you modify and save an active configuration, the version counter increases when it is saved.
To activate a stored version, choose Configuration _ Get other version.
You cannot directly activate version 0000. It is the result of converting the old control
tables to new configuration tables. To edit configuration version 0000, you must first
save this configuration as version 0001.
To do this, choose Configuration _ Save. The version counter increases to 0001.
Special features in the Graphical editor:
When the configuration is saved, the configuration transport routes are checked. This check
involves testing the delivery routes.
Checking the Transport Route Configuration
Features
There are 2 types of checks:
_ The configuration is checked against the settings of the transport control program and its
consistency is also checked.
_ The system checks to see if the deliveries go out from at least one consolidation.
_ When using multilevel deliveries, the system checks if the transport profile parameter
multileveldelivery is switched on for the SAP Systems involved (< Release 4.0A).
_ The system checks if the SAP Systems have at least Release 4.5A when using
enhanced transport control and if the accompanying transport profile parameter CTC is
switched on. The systems also checks if enhanced transport control is mixed with simple
transport control.
_ The effects of the configuration on the open tasks and requests is checked.
If the configuration of the transport routes is consistent, it is compared with open
requests. The system checks if these requests:
_ Require a different type (local or transportable request, repair or correction)
_ Require a new transport destination
_ Become inconsistent due to invalid object combinations
You cannot release inconsistent requests.
The displayed log lists all inconsistencies found. You can find detailed information in the long text
of the relevant message.
Activities
To check the consistency of the transport routes, choose Configuration _ Check _ Transport
routes.
To check the effects on open requests for the local SAP System, choose Configuration _ Check
_ Request consistency _ Local.
To check the effects on open requests for all SAP Systems, choose Configuration _ Check _
Request consistency _ In all systems. The effects of the configuration change on open requests
in accessible SAP Systems are checked.
Distributing and Activating Transport Route
Configurations
Prerequisites
When all checks have been completed, you can distribute and activate the configuration.
We recommend activating the configuration centrally from the domain controller. This
ensures that all SAP Systems in the transport domain have the same settings for the
transport routes.
To activate the transport routes in the systems of the transport domain, you need the
authorization S_CTS_CONFIG in all systems, which is contained in the profile
S_A.SYSTEM.
Procedure
To distribute and activate the transport route configuration, choose Configuration _ Distribute
and activate.
You are asked to enter your user ID and password in all connected SAP Systems.
For security reasons, the user TMSADM created by TMS, is not authorized to
activate transport routes by default. This is why a logon screen appears when you
activate transport routes from any system in the transport domain. To simplify this
procedure (which is recommended for a large number of systems), you can authorize
user TMSADM to activate transport routes. To do this, enter the additional profile
S_A.TMSCFG in the user maintenance.
_ The configuration has been activated from the controller in all SAP Systems.
_ The configuration status of all SAP Systems is displayed.
_ The request targets of open requests are changed according to the transport route
configuration.
Special Features of Multilevel Forwarding
The options for setting transport routes were expanded.
Until now you could only define recipient systems for consolidation systems. Therefore, a
transport route could only have two stages:
1. Development system _ Quality assurance system
2. Quality assurance system _ Production system
The first stage is the consolidation route, the second is the delivery route.
As of Release 4.0, there is multilevel forwarding. This allows you to define recipient systems for
recipient systems.
The transport control program tp implements this function.
tp also allows multilevel forwarding in Release 3.1G. But since 3.1G is compatible with 3.0C, this
function was deactivated in 3.1G.
If you want to use multilevel forwarding although your SAP System has a Release prior to
4.0A, you must note the following:
_ All transport control programs (tp) used must have at least Release 3.1G.
_ You must enter <SID>/multileveldelivery=1 in all transport profiles (TPPARAM) used.
Special Features of Extended Transport Control
Extended Transport Control has the following special features:
_ Client-specific transport routes (consolidation, delivery)
_ Target groups
_ Assignment of clients to transport layers
You cannot use client-specific and client-independent transport routes together. All the SAP
Systems linked to each other by transport routes must have either a uniform client-specific or
client-independent connection.
When you define transport routes to systems in other domains, Extended Transport
Control is only tested in the other domain, it is not activated automatically. If the
other domain has a different client control setting an appropriate warning appears.
Activating Extended Transport Control
Extended Transport Control is activated automatically, depending on the transport routes.
Setting System Attributes
You can make the following settings for an SAP System:
_ Transport strategy, see Choosing a Transport Strategy
_ Quality assurance, see Configuring the QA Approval Procedure
_ Standard transport layer, see Changing the Standard Transport Layer of an SAP System
Changing the Standard Transport Layer of an SAP
System
Prerequisites
A standard transport layer is assigned to each SAP System.
Procedure
To change the standard transport layer:
1. Go to the TMS transport route overview.
2. Position the cursor on the SAP System.
3. Choose Edit _ System _ Change.
The dialog box Change System Attributes appears.
4. Choose the tab Standard transport layer.
5. Change the transport layer of the SAP System.
If you have activated extended transport control, you can set the standard transport layer
for each client.
a. Choose Assign client.
b. Specify the transport layer for the client.
6. Choose Copy.
7. Save the configuration.
Result
The standard transport layer has been copied to the transport route configuration for the chosen
SAP System.
Choosing a Transport Strategy
Use
Before you transport requests between systems, choose a transport strategy that meets your
requirements.
The transport strategy is set by default to queue-controlled mass transports. If you
want to work with single transports or workflow-controlled transports instead,
change the configuration as described here.
Prerequisites
You have configured transport routes between the systems.
Procedure
1. In the TMS initial screen, choose . The screen Display Transport Routes appears
displaying the existing transport routes in the transport domain.
2. Switch to the change mode by choosing Configuration _ Display __ Change.
3. Position the cursor on the SAP System for which you want to choose a transport strategy.
4. Choose Edit _ System _ Change. The dialog box Change System Attributes appears.
5. Choose the tab System attributes and choose your transport strategy.
Within the same system group you must set all systems either to Queuecontrolled
transports or Workflow-controlled transports. If you choose the strategy
Workflow-controlled transports for one system in a system group, TMS also chooses
this strategies for all other systems in the group. You can, however, set Mass
transports or Single transports for individual systems.
6. Choose Copy.
7. Choose Configuration _ Distribute and activate.
Result
The following settings are made, according to transport strategy:
_ Mass transports
By default, the import option Leave transport request in queue for later import is
activated.
The import option Leave transport request in queue for later import causes requests
that have been imported as single transports to be imported in the correct order in
Choosing a Transport Strategy
98 April 2001
the next import of all requests. This option is useful if you have to make preliminary
imports for individual requests. This prevents older objects from being imported at
the next regular import of all the requests (overshooter problem).
_ Single transports
_ By default, the import option Leave transport request in queue for later import is
deactivated.
If you supply a system only with single transports, this option is not useful since the
requests remain in the queue after the import and have to be manually deleted from
the import queue.
_ The pushbutton bar in the import queue changes according to the requirements of the
single import strategy (for example, it contains a select function).
_ In the import queue display, the function Queue _ Start import is only available if you
have selected one or more projects using the filter function. This prevents accidentally
importing all the requests in the queue.
_ Workflow-controlled transports
_ Transport proposals are created automatically when requests are exported.
_ The import options correspond to those for single transports.
_ Imports become linked to the processing of transport proposals in the TMS worklist.
_ A warning appears in the import queue if you try and make transports without using the
transport workflow.
Transport Control Parameters
The following parameters for the transport control program and the Change and Transport
System (CTS) are set according to the chosen transport strategy:
Parameter Value for Mass
Transports
Value for Single
Transports
Value for Workflow-
Controlled
Transports
IMPORT_SINGLE_ONLY 0 1 1
NO_IMPORT_ALL 0 1 1
IMPORT_SINGLE_STRATE
GY
0 1 0
WORKFLOW_STRATEGY 0 0 1
REPEATONERROR 9 8 8
STOPONERROR 9 9 9
You can display these parameters in the TMS system overview. To do this, position the cursor on
the appropriate system and choose SAP System _ Display. The tab Transport tool contains all
the profile parameters.
Do not manually change the parameters that are relevant to the transport strategy.
TMS generates these parameters each time the transport route configuration is
changed.
Configuring the Transport Workflow
Use
Use the transport workflow to automate your transport process. It is an efficient way of
transporting selected requests in your system landscape. An explicit approval step before the
import guarantees the quality of the target system.
Prerequisites
You must first decide which system you want to configure as the Workflow Engine. The
system must have the following criteria, which are listed in order importance:
1. High availability
2. Higher release
3. Low to middle system load
These prerequisites are usually met by the Quality Assurance system.
All the functions of the transport workflow are processed locally in the Workflow
Engine. All tasks are processed here and then sent to the logon systems of the
users.
Therefore, for anyone who uses the transport workflow, you must create a user with
the authorization S_CTS_PROJEC in the system/client in which the Workflow
Engine is configured.
Procedure
To configure the transport workflow:
1. Log on to the SAP System that functions as the transport domain controller.
2. Call Transaction STMS and then choose to display the system overview.
3. Choose to display the transport domain.
4. Choose the tab Workflow Engine.
5. Switch to change mode by choosing and select the option Local domain under Location.
6. Under RFC address, enter the SAP System, the client, and the target host for your Workflow
Engine. Save your entries and distribute the configuration change. Log on to the system that
is to be configured as the Workflow Engine. The system performs the following actions:
_ Creates the user TMSADM_WF
_ Generates the RFC destinations required for the Workflow Engine
_ Sends all systems in the transport domain the address data of the Workflow Engine
_ Performs workflow Customizing in the Workflow Engine
7. Check the Workflow RFC connection.
