SAP Subscribe | Add to Favorites Note 28781 - Central transport directory NT/UNIX

Symptom:

This note describes all steps required to set up a common transport directory between UNIX, AS/400, and WINDOWS.

Other terms

WINDOWS TRANSPORT DIRECTORY MIXED SYSTEMS SAMBA AS/400

Solution

Overview

Setting up a central transport directory WINDOWS/UNIX
1. Problem during transport between UNIX and Windows

2. Additional necessary software for UNIX

3. Actions for configuration with TMS
a) Maintain the transport profile
b) Change instance profile of SAP systems under Windows
c) Adjust the SAP profiles to UNIX format

4. Actions for configuration without TMS
a) Tools required under Windows
b) Setting the binary mode for SAP tools
c) Maintain the transport profile TPPARAM
d) Change instance profile of SAP systems under Windows
e) Adjust the SAP profile to UNIX format

5. Example for SAMBA configuration file

6. Example for a mixed transport file

Explanation of terms:

1. TMS:
Transport Management System (transaction STMS)

2. Transport Profile:
The name of your transport profile depends on whether you have configured the TMS. The transport profile is by default located in the directory \usr\sap\trans\bin.
When using TMS: TP_DOMAIN_.PFL
When not using TMS: TPPARAM

Setting up a central transport directory NT/UNIX

1. Problem during transport between UNIX and WINDOWS
When you use the transport system, various files are created in the transport directory which are written by the kernel, tp.exe and R3trans.exe, among other things.
The files in the log, buffer and cofiles subdirectories are opened in the default mode (= text mode), while the files in the transport subdirectory data are written as binary data.
When you write the files in text mode, there are the following differences between the two operating systems:
UNIX writes a linefeed at the end of every line.
WINDOWS writes a carriage return/linefeed at the end of every line.

When you write files in binary mode, a linefeed is written at the end of every line under both UNIX and WINDOWS.
Consequently, files which are written in text mode under WINDOWS are not legible under UNIX, and vice versa.

To set up a common transport directory for UNIX and Windows, you select the binary mode as default mode for writing to the files. This can be set using environment variables as well as profile parameters.
For transports between systems based entirely on Windows that are executed in standard text mode, these parameters are not required.

2. Additionally required software for UNIX systems
Currently, Windows does not have a hierarchical file system like UNIX. There is also no way to create soft links. Thus, file systems on Windows machines cannot be attached to local UNIX trees or vice versa. In order to still enable bidirectional access to the file systems, additional software has to be installed.
This software must meet the following requirements:

• There must be a distinction between upper and lowercase in filenames, as filenames are case-sensitive in UNIX.

• The authentication in the other system must be possible using the LanManager API.

• The software must be able to display the contents of directories, regardless of how you access or link to these directories. Only use software that can export soft links.
  
  Because LanManager has a large portion of the PC network market, software has been developed for UNIX systems to allow access to LanManager networks. In the meantime there is server software for almost all UNIX variants, which allows the UNIX system to appear as LanManager as far as the PC is concerned. Many hardware manufacturers offer this type of LanManager software. However, SAP cannot recommend one particular one that you should use. However, if you decide on a product, ensure that the three above-mentioned requirements are met by this software.
  
  SAP uses the LanManager server called SAMBA (by Andrew Tridgell), which can be acquired free of charge on the Internet. However, SAP does not support SAMBA.
  
  Internet address:
  http://samba.anu.edu.au/samba
  
  The LanManager server SAMBA provides file services. You can access the Windows files in exactly the same way as though you were in a UNIX shell.

• SAMBA ensures the distinction between upper and lowercase in in filenames.

• The SAMBA server can be configured so that it relies on the authentication from a Windows Server at logon (Windwows Server Authentication).
  The assignment of the UNIX user to the corresponding Windows user is
  stored in a table on the SAMBA server. The user check is then performed by Windows. You can find information in the section "Example SAMBA configuration file for Windows authentication"

3. Actions of configuration with TMS

a) Maintain the transport profile

• Log on to the transport domain controller and call transaction STMS.

• Then choose 'Overview -> System' and choose a system by double-clicking. Then choose 'Configuration -> Display/Change -> Transport tool -> Edit -> Insert row'.

• Record the following entries:
  Global Parameters Value OpSys
  x ABAPNTFMODE b wnt
  x transdir wnt
  
  Example:
  Global Parameters Value OpSys
  x ABAPNTFMODE b wnt
  x transdir \\trans01\trans4\ wnt
  A99/r3transpath \R3trans.exe wnt
  A99/sapevtpath \sapevt.exe wnt
  A99/system_pf \default.pfl wnt
  
  The parameter ABAPNTFMODE determines the mode for opening the files which is used by tp and all the tools called from tp.

• Afterwards, save the configuration. Choose 'Configuration -> Save' and go back to the system overview.

• Then choose 'Extras -> Distribute TMS configuration'.

b) Changes instance profile of SAP systems under Windows NT
For any SAP system under Windows that is going to use the central transport directory the following entries have to be made in the system-specific instance profile of the respective system:

• Mode to open the files, that is used by the SAP kernel.
  abap/NTfmode=b

• Set DIR_TRANS on UNIX transport directory
  DIR_TRANS=\\trans01\trans4 (without backslash)

• Set DIR_EPS_ROOT on transport directory for transaction SPAM
  DIR_EPS=\\trans01\trans4\EPS

• Do not set the parameter DIR_EPS directly in the profile - this parameter is generated automatically depending on the parameter DIR_EPS_ROOT.

• Stop the respective SAP system under Windwos and then restart it.
  

c) Adjustments of SAP profiles to UNIX format
The profiles of all systems running under Windows have to be converted to binary format.
For this, log to each system in SAP and execute transaction RZ10.
Choose 'Utilities -> Import profiles -> of active servers'.
The profiles are saved in binary format.

4. Actions for configuration without TMS

a) Tools required under Windows
For access to a common transport directory the editor SAPPAD is required:
This editor is located in the executable directory of your system and can interprete UNIX as well as WINDOWS file formats.

b) Setting binary mode for SAP tools
As of Release 4.5A:
Enter the following parameters into your transport profile:
ABAPNTFMODE=b

For Releases < 4.5A:
Set the environment variable abap/NTfmode=b in the user environment for the users under whom the transport program tp.exe or R3trans.exe is started.
The environment variable has to be entered in any case for the user under whom the kernel was started (ADM oder SAPService).
(In the Control Panel -> System -> User Environment variable).

The program NTENV2REG.EXE is stored in your SAP kernel directory.
Call the program to declare the user environment to the kernel. This action has to be performed on all machines on which transports are performed.

c) Maintain the transport profile TPPARAM
Enter the following transport parameter into your transport profile:

• Path of transport parameter
  wnt|transdir=

• Example:
  wnt|transdir = \\trans01\trans4\
  wnt|A99/r3transpath=\\\R3trans.exe
  wnt|A99/sapevtpath=\\\sapevt.exe
  wnt|A99/system_pf=\\nt1\sapmnt\A99\sys\profile\default.pfl
  The transport profile has to be saved with SAPPAD in UNIX-Format. Choose Options -> Save As Unix File.
  

d) Changing the instance profile of SAP systems under Windows
For any system that is going to use the central transport directory the following system-specific instance profiles of the respective system have to be included:

• Mode for opening the files that is used by SAP kernel.
  abap/NTfmode=b

• Set DIR_TRANS on UNIX transport directory
  DIR_TRANS=\\trans01\trans4

• Set DIR_EPS_ROOT to transport directory for transaction SPAM
  DIR_EPS_ROOT=\\trans01\trans4\EPS

• Do not set parameter DIR_EPS in the profile itself - it is
  automatically generated depending on the parameter DIR_EPS_ROOT.

• Stop the respective R/3 system as well as the Service SAP
  _ (for this you use Control Panel->Services).
  

e) Adjustments of R/3 profiles to UNIX format
The profiles of all systems running under Windows that are going to use the central transport directory have to be converted to binary format.
For this you log on to each system in SAP and execute transaction RZ10.
Choose 'Utilities -> Import profiles -> of active servers'.
This saves the profiles in the UNIX format.

5. Example SAMBA configuration file for Windows authentication

----------> Windows Server Authentication
; Configuration example file for samba using computer pswdf004 as
; password server
[global]
; SECURITY OPTION guest account: the guest has the file access
; rights of this UNIX-user
guest account = nobody

debug level = 0
security = server
password server = pswdf004
getwd cache = yes
wide links = no
password level = 8
case sig names = yes
preserve case = yes
case sensitive = yes
read prediction = yes

[transdir]
comment = us0011:/usr/sap/trans
path = /usr/sap/trans
; SECURITY OPTION public: all users can access the share as a guest
; no password is checked
public = yes
; SECURITY OPTION writable: files + directories can
; be changed if writable = yes
writable = yes
; SECURITY OPTION browsable: Share is visible if browsable = yes
browsable = yes
create mask = 0664
map hidden = no
map system = no
preserve case = yes
wide links = yes
; SECURITY OPTION allow hosts: only specified hosts can access the
; share
allow hosts = us0011

6. Example of a mixed transport profile

ABAPNTFMODE = b
transdir = /usr/sap/trans/
wnt|transdir = \\trans01\trans4\
syslog = SLOG$(syear)$(yweek).$(system)
alllog = ALOG$(syear)$(yweek).$(system)
r3transstat = $(transdir)log/STATLOG.$(system).#.$(yweek)

BIN/dbhost = hs0055
BIN/dbname = BIN

BIN/r3transpath = /bas/$(system)/exe/dbg/$(cpu)/R3trans
wnt|BIN/r3transpath = \\NTPC\sapmnt\bin\sys\exe\run\R3trans.exe

sapevtpath = /bas/$(system)/exe/dbg/$(cpu)/sapevt
wnt|BIN/sapevtpath = \\NTPC\sapmnt\bin\sys\exe\run\sapevt.exe

BIN/system_pf = /bas/$(system)/profile/DEFAULT.PFL
wnt|BIN/system_pf = \\NTPC\sapmnt\bin\sys\profile\BIN_D53_NTPC
BIN/impdp_by_event = yes