Symptom
This note describes all steps required to set up a common transport directory between UNIX, AS/400, and WINDOWS NT.
Additional key words
Windows NT, transport directory, mixed systems, Samba, AS/400
Cause and prerequisites
..
Solution
Overview
Setting up a central transport directory NT/UNIX
1. Problem during transport between UNIX and Windows NT
2. Additional necessary software for UNIX
3. Actions for configuration with TMS
a) Maintain the transport profile
b) Change instance profile of R/3 systems under Windows NT
c) Adjustments of R/3 profiles to UNIX format
4. Actions for configuration without TMS
a) Tools required under Windows NT
b) Setting the binary mode for R/3 tools
c) Maintain the transport profile TPPARAM
d) Change instance profile of R/3 systems under Windows NT
e) Adjustments of R/3 profiles 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 transportprofile in is located inthe directory\usr\sap\trans\bin in the standard system.
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 NT
When you use the transport system, various files are created in the transport directory which are writtenby 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 thefiles in the transport subdirectory are written as binary data.
When you write the files in text mode, there are the following differences between the two operating systems:
UNIXwrites a linefeed at the end of every line.
WINDOWS NT writesa 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 NT.
Consequently, files which are written in text mode under WINDOWS NT are not legible under UNIX, and vice versa.
To set up a common transport directory for UNIX and Windows NT, you select the binary mode as default mode for writing to the files. This can be setvia environment variables as well as via profile parameters.
For transports between systems based entirely on Windows NT that are executed in standard text mode, these parameters are not required.
2. Additionally required software for UNIX systems
Currently, NTdoes not have a hierarchical file system like UNIX. There
is also no way to create soft links. Thus, file systems on NT machines cannot be attached to local UNIX trees or vice versa. In order to still allow a bidirectionalaccess to the file systems, additional software must 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 via the LanManager API.
- The software must be able to display the contents of directories, regardless of how you access or link to thesedirectories. 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 fulfilled by this software.
SAP uses the LanManager server called SAMBA(by AndrewTridgell), which can be acquiredfreeof charge via the Internet. However, SAP does not support SAMBA.
Internetaddress:
The LanManager server SAMBA provides file services. You can access the NT files in exactly the same way as though you were in a UNIX shell.
- SAMBA ensures the distinction between upper and lowercase in filenames.
- The SAMBA server can be configured so that it relies on the authentication from a Windows NT Server at logon (NT Server Authentication).
The assignment of the UNIX user to the corresponding NT user is stored in a table on the SAMBA server. The user check is then performed by NT. You can find information in the section "Example SAMBA configuration file for NT 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 followingentries:
Global Parameters Value OpSys
xABAPNTFMODE b wnt
xtransdir 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 which are called from tp.
- Afterwards, save the configuration via 'Configuration -> Save' and go back to the system overview.
- Then choose 'Extras -> Distribute TMS configuration'.
b) Changesinstance profile of R/3 systems under Windows NT
For any R/3 system under Windows NT that is going to use the central transportdirectory 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 R/3 kernel.
abap/NTfmode=b
- Set DIR_TRANS on UNIX transport directory
DIR_TRANS=\\trans01\trans4 (without backslash)
- SetDIR_EPS on subdirectory of transport directory for Transaction SPAM
DIR_EPS=\\trans01\trans4\EPS\--------
- DIR_EPS_ROOTfortransportdirectory set for TransactionSPAM
DIR_EPS_ROOT=\\trans01\trans4\EPS
Stop the respectiveR/3 system under Windows NT and then restart it.
c) Adjustments of R/3 profiles to UNIX format
The profiles of all systems running under Windows NT have to be converted to binary format.
For this,login on any system in R/3 and execute transactionRZ10.
Choosethere 'Utilities -> Import profiles -> of active servers'.
Thus the profiles are saved in binary format.
4. Actions for configuration without TMS
a) Tools required under Windows NT
For access on 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 NT file format.
b) SettingbinarymodeforR/3tools
As ofRelease4.5A:
Enter the following parameters into your transport profile:
ABAPNTFMODE=b
ForReleases < 4.5A:
Set the environment variable abap/NTfmode=b in the user environment for the users under whomthe transport program tp.exe or R3trans.exe is started.
The environment variable must be entered in any case for the user under whom the kernelwasstarted (ADM oder SAPService).
(In theControlPanel -> System -> User Environment variable).
The programNTENV2REG.EXE is stored in your R/3 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 parameter 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
Thetransport profile has to be saved with SAPPAD in UNIX-Format. Forthis you choose Options->Save As Unix File.
d) Changesinstance profile of R/3 systems under Windows NT
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 R/3 kernel.
abap/NTfmode=b
- Set DIR_TRANSonUNIXtransportdirectory
DIR_TRANS=\\trans01\trans4
DIR_EPS_ROOTfor transport directory set for Transaction SPAM
DIR_EPS_ROOT=\\trans01\trans4\EPS
- Youmustnotsetparameter DIR_EPSin the profileitself - it is
automaticallygenerated depending on the parameter DIR_EPS_ROOT.
Stop the respectiveR/3 system aswellas the ServiceSAP_ (for this you use Control Panel->Services). Afterwards restart both.
e)Adjustments of R/3 profiles to UNIX format
The profiles of all systems running under Windows NT that are going to use the central transportdirectory have to be converted to binary format.
For this you logonto each system in R/3 and execute TransactionRZ10.
There,select 'Utilities -> Import profiles -> of active servers'.
This saves the profiles in the UNIX format.
5. Example SAMBA configuration file for NT authentication
---------->NT Server Authentication
; Configuration example file forsambausing computer pswdf004as
;password server
[global]
;SECURITYOPTIONguest account:theguest has the file access
;rights of thisUNIX-user
guestaccount= nobody
debuglevel = 0
security= server
passwordserver = pswdf004
getwdcache = yes
widelinks= no
passwordlevel = 8
case sig names=yes
preserve case= yes
casesensitive = yes
read prediction = yes
[transdir]
comment= us0011:/usr/sap/trans
path= /usr/sap/trans
;SECURITY OPTION public: all userscanaccess the share as a guest
;no password ischecked
public= yes
; SECURITY OPTION writable: files + directoriescan
; bechangedif writable= yes
writable=yes
;SECURITYOPTIONbrowsable: Shareisvisible if browsable= yes
browsable = yes
create mask = 0664
map hidden = no
mapsystem= no
preserve case= yes
widelinks = yes
; SECURITY OPTION allow hosts: only specified hosts can access the
; share
allow hosts = us0011
1. 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
Source code corrections
