starting with Version 7.0, the SAP Web Dispatcher is able to support logon groups and URL prefixes for the J2EE engine.
Please be aware of the fact that the SAP Web Dispatcher 7.0 can only support logon groups and URL prefixes either for ABAP or J2EE engine. So the customer should not enable J2EE logon groups in a Web Dispatcher in front of a double stack system. Otherwise, stateful web applications on the ABAP stack will not work correctly.
Tina already changed the documentation accordingly. You will find the information in the help portal after it was released:
http://help.sap.com/saphelp_nw70/helpdata/EN/62/5f374ff72c40478fcba2bb4fa79ddf/content.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/45/3dbe11a82b6bf1e10000000a1553f6/content.htm
(seek for "wdisp/enable_j2ee_groups")
The Web Dispatcher 7.10 will support logon groups for ABAP and Java simultaneously (in front of double stack systems).
Tuesday, April 29, 2008
Monday, April 28, 2008
Central monitoring setup for an Enterprise Portal by using Solution Manager 4.0
Please find link of Central monitoring setup for an Enterprise Portal by using Solution Manager 4.0 ..
https://websmp205.sap-ag.de/diagnostics
https://websmp205.sap-ag.de/diagnostics
BIN BIN2 collation
BIN BIN2 collation
Reference note: 600027 ,505906
If the collations do not match, proceed as follows depending on the
case that applies for your system: :
- Case 1: Database collation: SQL_Latin1_General_CP850_BIN
Target Server collation: SQL_Latin1_General_CP850_BIN2
a) In this case, attach the database.
b) Make sure that no user connects and uses this database.
c) Re-run InstColl.exe with the following command line:
InstColl -S -D
The special -D option allows you to convert only one database.
This should finish within a very short time (<3 minutes)
You can now use the SAP database in its new location.
- Case 2: Database collation: SQL_Latin1_General_CP850_BIN2
Target Server collation: SQL_Latin1_General_CP850_BIN
a) Back up all databases on the target server.
b) Make sure that you also have a backup (or copy) of the database
you are migrating.
c) Apply SP4.
d) Run InstColl.exe against the server (do not use the -D option).
e) Attach the database.
Reference note: 600027 ,505906
If the collations do not match, proceed as follows depending on the
case that applies for your system: :
- Case 1: Database collation: SQL_Latin1_General_CP850_BIN
Target Server collation: SQL_Latin1_General_CP850_BIN2
a) In this case, attach the database.
b) Make sure that no user connects and uses this database.
c) Re-run InstColl.exe with the following command line:
InstColl -S
The special -D option allows you to convert only one database.
This should finish within a very short time (<3 minutes)
You can now use the SAP database in its new location.
- Case 2: Database collation: SQL_Latin1_General_CP850_BIN2
Target Server collation: SQL_Latin1_General_CP850_BIN
a) Back up all databases on the target server.
b) Make sure that you also have a backup (or copy) of the database
you are migrating.
c) Apply SP4.
d) Run InstColl.exe against the server (do not use the -D option).
e) Attach the database.
Unix guide
© 2000 UNIXguide.net, All Rights Reserved. Hermelito Go (Last Update: Thursday, 11−Apr−2002 14:32:33 PDT )
Directory Mappings AIX FreeBSD HP−UX LINUX(RedHat) SOLARIS Tru64
Root filesystem / {/dev/hd4} / {/dev/ad0s1a} / {/dev/vg00/lvol1} / {/dev/sda1} / {/dev/vx/dsk/rootvol} / {/dev/rz0a}
Home Directory /home {/dev/hd1} /home {/dev/vg00/lvol4}
/export/home
/dev/vx/dsk/home}
/tmp {/dev/hd3} /tmp {/dev/vg00/lvol6}
/tmp
/dev/vx/dsk/swapvol}
/usr {/dev/hd2} /usr {/dev/ad0s1f} /usr {/dev/vg00/lvol7} /usr /usr {/dev/rz0g}
/var {/dev/hd9var} /var {/dev/ad0s1e} /var {/dev/vg00/lvol8} /var
Sample configuration
files
− /usr/newconfig
User Accounts AIX FreeBSD HP−UX LINUX(RedHat) Solaris Tru64
Password files
/etc/passwd
/etc/security/passwd
/etc/passwd
/etc/master.passwd
/etc/passwd
/tcb/files/auth/r/root
/etc/passwd
/etc/shadow
/etc/passwd
/etc/shadow
/etc/passwd
Groups file
/etc/group
/etc/security/group
/etc/group
/etc/group
/etc/logingroup
/etc/group /etc/group /etc/group
Maximum # of user ID 4294967295 65535 2147483647 65535 2147483647 65535
Allow/Deny remote
login
/etc/security/user
{rlogin=true}
/etc/ttys
{secure}
/etc/securetty
{console}
/etc/securetty
{ttyp1}
/etc/default/login
{CONSOLE=/dev/console}
/etc/securettys
{ttyp1}
User nobody's id # 4294967294 65534 −2 99 60001 & 65534(nobody4) 65534
Group nobody's id # 4294967294 65534 −2(nogroup) 99 60002 & 65534(nogroup) 65534
Recover root
password
boot from CD/Tape
Installation/Maintenance
Start Limited Shell
getrootfs hdisk0
vi /etc/security/passwd
ok boot −s
passwd root
>boot
Interact with IPL ? Y
ISL>hpux −iS
passwd root
{lilo}
control−x
linux S
passwd root
{grub}
c
kernel vmlinuz−2.4.9−13 single
ro root=/dev/hda8
initrd /initrd−2.4.9−13.img
boot
passwd root
boot cdrom −s
mkdir /tmp/a
mount /dev/c0t0d0s0
/tmp/a
vi /tmp/a/etc/shadow
press the HALT Button or
(Control−P)
>>>boot −fl s
lsmbstartup
/sbin/bcheckrc
passwd root
Create new user mkuser adduser useradd useradd useradd useradd
Delete user rmuser rmuser userdel userdel userdel userdel
List users lsuser −f ALL logins logins
Modify user account chuser −a usermod usermod usermod usermod
General Commands AIX FreeBSD HP−UX LINUX(RedHat) Solaris Tru64
Unique host ID hostid uname −i hostid hostid hostid
Administrator smit sam linuxconf admintool
Performance monitor
top
monitor
top
top
glance
top top top
System activity
reporter
sar sa sar sar {sysstat} sar /usr/opt/svr4/bin/sar
Virtual Memory
statistics
vmstat vmstat vmstat vmstat vmstat vmstat
I/O statistics iostat iostat iostat iostat {sysstat} iostat iostat
Error logs
alog −o −t boot
errpt
dmesg dmesg dmesg dmesg uerf −R −o full
Physical RAM 1TB 4TB 64 GB {>2.3.24} 16TB 4TB
Shared Memory 2.75GB 8TB sysctl kernel.shmmax
Process Data Space 2GB 4GB 900 MB
Swap device /dev/hd6 /dev/ad0s1b /dev/vg00/lvol2 /dev/sda2 /dev/vx/dsk/swapvol /dev/rz0b
Swap file type /etc/swapspaces swap swap partition type 82 swap raw
Display swap size lsps −a swapinfo swapinfo −a free swap −l swapon −s
Activate Swap swapon −a swapon −a swapon −a swapon −a swap −a swapon −a
Printers AIX FreeBSD HP−UX LINUX Solaris Tru64
Printer Queues /etc/qconfig /var/spool/print /etc/lp/interface/* /var/spool/lpd/lp/* /etc/lp/interfaces/* /usr/spool/lpd
Stop LP stopsrc −s lpd lpshut /etc/init.d/lpd stop /usr/lib/lp/lpshut /sbin/init.d/lpd stop
Start LP startsrc −s lpd lpd lpsched /etc/init.d/lpd start /usr/lib/lp/lpsched /sbin/init.d/lpd start
Submit print jobs
enq
lp
lpr
qprt
lp lp lpr
lp
lpr
lp
lpr
LP statistics
enq −A
lpq
lpstat
qchk
lpq lpstat lpq lpstat lpstat
Remove print jobs
cancel
lprm
qcan
enq −x
cancel
lprm
cancel lprm
cancel
lprm
cancel
lprm
Add printer queue smit mkpq lpadmin −p pq printtool lpadmin −p pq lprsetup
Remove Printer queue smit rmpq lpadmin −x pq lpadmin −x pq lprsetup
Make default printer export LPDEST="pq" lpadmin −d pq lpadmin −d pq export PRINTER="lp"
TCP/IP AIX HP−UX LINUX(RedHat) Solaris Tru64
Network IP
configuration
lsattr −E −l inet0 /etc/rc.conf /etc/rc.config.d/netconf /etc/sysconfig/network−scripts/
/etc/hostname.*
/etc/inet/*
/etc/defaultrouter
/etc/rc.config
Hosts IP addresses /etc/hosts /etc/hosts /etc/hosts /etc/hosts /etc/inet/hosts /etc/hosts
Name service switch /etc/netsvc.conf /etc/host.conf /etc/nsswitch.conf /etc/nsswitch.conf /etc/nsswitch.conf /etc/svc.conf
Network parameters no −a sysctl ndd −h sysctl −a grep net ndd /dev/[tcpip] ?
Routing daemon gated routed gated routed in.routed routed
NIC Configurations ifconfig −a ifconfig −a lanscan −v ifconfig −a ifconfig −a ifconfig −a
Secondary IP Address ifconfig en0 alias IP ifconfig xl0 alias IP ifconfig lan0:1 IP
modprobe ip_alias
ifconfig eth0:1 IP
ifconfig hme0:1 IP up ifconfig ln0 alias
Login prompt
HERALD @
/etc/security/login.cfg
telnetd −b /etc/issue /etc/issue
BANNER @
/etc/default/telnetd
/etc/issue
Increase the # of
pseudo−terminals
odmget −q "attribute=num
and
uniquetype=pty/pty/pty"
PdAt sed "s/0−64/0−512/"
odmchange −q
"attribute=num and
uniquetype=pty/pty/pty"
−o PdAt
chdev −l pty0 −anum=256 −P
reboot
rebuild your kernel with these
new values NPTY=#
NSTRPY=#
reboot
insf −d ptys −n #
insf −d ptym −n #
insf −d pts −s # −e −v
cd /dev
./MAKEDEV −v pty
{/etc/system}
set pt_cnt = # {SYSV}
set npty = # {BSD}
{/etc/iu.ap}
ptsl 0 # ldterm ttcompat
halt
boot −r
cd /dev
./MAKEDEV PTY_1
Maximum # of ptys 512 {MAXUSERS} 256
176 {BSD}
3000 {SYSV}
8192
Remote Shell
remsh
rsh
rsh remsh rsh rsh rsh
YP/NIS service
binder
/usr/lib/netsvc/yp/ypbind /usr/sbin/ypbind /usr/lib/netsvc/yp/ypbind /sbin/ypbind /usr/lib/netsvc/yp/ypbind /usr/sbin/ypbind
System Files AIX FreeBSD HP−UX LINUX(RedHat) Solaris Tru64
NFS exported /etc/exports /etc/exports /etc/exports /etc/exports
/etc/dfs/dfstab
/etc/dfs/sharetab
/etc/exports
NFS Client mounted
directories
/etc/xtab /etc/xtab /var/lib/nfs/xtab /etc/rmtab /var/adm/mountdtab
Max File System 128 GB 128 GB 2 TB
1 TB
8000 TB {vxfs}
128 GB {<= 3.2G}
512 GB {>= 4.0}
16 TB {advfs}
Max File Size 64 GB 128 GB
2 GB {512B block size}
8192 GB {8KB block size}
1 TB
2 GB {=
128 GB {<= 3.2G}
512 GB {>= 4.0}
16 TB {advfs}
Max # File
Descriptors
64 K 60~ K sysctl fs.file−max 64 K 64 K
DISK/LVM Commands AIX FreeBSD HP−UX:Disk &Filesystem LINUX(RedHat) SOLARIS Tru64
Filesystem table /etc/filesystems /etc/fstab /etc/fstab /etc/fstab /etc/vfstab /etc/fstab
Free disk blocks df −k df −k bdf df −k df −k df −k
Device listing lsdev −C /sbin/ioscan cat /proc/devices sysdef
Disk information bootinfo −s hdisk# fdisk −v ad0 diskinfo /dev/rdsk/c#t#d# cat /proc/scsi/scsi0/sda/model
format −d c#t#d#
format>current
format>inquiry
file /dev/rrz0c
Disk Label lspv −l hdisk# disklabel ad0 pvdisplay −v /dev/dsk/C#t#d# fdisk −l prtvtoc disklabel −p rz0
LVM Concepts Partition sub disk logical extents logical extents sub disk sub disk
Volume Volume logical volume logical volume Volume Volume
Plex Plex Plex
Volume group volume group volume group disk group disk group
Journal Filesystem
type
jfs vxfs ext2 vxfs advfs
Default volume group /dev/rootvg /dev/vg00 /dev/vx/dsk/rootdg /dev/vol/rootdg
Display volume group lsvg −l rootvg vgdisplay −v vg00 vgdisplay −v vxprint −l −g rootdg volprint −l −g rootdg
Modify physical
volume
chpv pvchange pvchange
Prepare physical
disk
mkdev −c disk −l hdisk# pvcreate pvcreate vxdiskadd voldiskadd
List physical volume lspv vinum ld pvdisplay pvdisplay vxprint −dl volprint −dl
Remove disk from
volume group
reducevg vgreduce vgreduce vxdg rmdisk voldg rmdisk
Move logical volumes
to another physical
volumes
migratepv
vinum move −f drive
object
pvmove pvmove vxassist move volassist move
Create volume group mkvg vgcreate vgcreate vxdg init voldg init
Remove volume group vgremove vgremove
Volume group
availability
chvg
varyonvg
varyoffvg
vgchange vgchange
Restore volume group vgcfgrestore vgcfgrestore
Exports volume group exportvg vgexport vgexport vxdg deport voldg deport
Imports volume group importvg vgimport vgimport vxdg import voldg import
Volume group listing lsvg vgscan vgscan
Change logical
volume
characteristics
chlv lvchange lvchange vxedit set voledit set
List logical volume lslv vinum lv lvdisplay lvdisplay vxprint −vl volprint −vl
Make logical volume mklv lvcreate lvcreate vxassist make volassist make
Extend logical
volume
extendlv lvextend lvextend vxassist growto volassist growto
Reduce logical
volume
AIX reduce LV lvreduce lvreduce vxassist shrinkto volassist shrinkto
Remove logical
volume
rmlv vinum rm vol lvremove lvremove vxedit rm
voledit −g rootdg −rf rm
vol1
Prepare boot volumes bootlist −m normal lvlnboot lilo vxbootsetup
Remove boot volumes lvrmboot
Extend File system chfs −a size=# /mt
extendfs /dev/vg00/lvol8
fsadm −F vxfs −b {LE * 1024} /mt
resize2fs
vxva
mkfs −M
Reduce/Split mirrors rmlvcopy lvsplit lvsplit
Merge mirrors lvmerge lvmerge
Create mirrors mklv −c 2 vinum mirror drive lvcreate −m 1 vxassist mirror
volassist make vol 100mb
mirror=true
Add mirrors mklvcopy lv 2 lvextend −m 1
Create striped
volumes
mklv −u 3 −S 64K vinum stripe drive lvcreate −i 3 −I 64 lvcreate −i 3 −I 64
vxassist make vol 100mb
layout=raid5
volassist make vol 100mb
layout=stripe
System recovery tape mksysb −i /dev/rmt0 /opt/ignite/bin/make_recovery /usr/sys/bin/btcreate
Backup savevg −i rootvg vinum saveconfig fbackup tar cvf /dev/rst0 / ufsdump vdump
Restore restvg frecover tar xvf /dev/rst0 ufsrestore vrestore
MISC AIX FreeBSD HP−UX LINUX(RedHat) SOLARIS Tru64
Startup script /etc/rc /etc/rc /sbin/rc /etc/rc.d/rc /sbin/init.d /sbin/init.d
Kernel /usr/lib/boot/unix_up /kernel /stand/vmunix /boot/vmlinuz /kernel/genunix /vmunix
Kernel Parameters lsattr −E −l sys0 sysctl −a
sysdef
kmtune
kmsystem
sysctl −a sysdef −i
sysconfig
dxkerneltuner
Reconfigure the
kernel chdev −l sys0 −a
cd /sys/i386/conf
vi KERNEL
config KERNEL
cd ../../compile/KERNEL
make depend
make
make install
cd /stand/build
/usr/lbin/sysadm/system_prep −v
−s system
vi system
mk_kernel −s system
cd /stand
mv system system.prev
mv vmunix vmunix.prev
mv dlkm dlkm.prev
mv /stand/build/system system
kmupdate /stand/build/vmunix_test
cd /usr/src/linux
make mrproper
make menuconfig
make dep
make clean
make bzimage
make install
make modules
make modules_install
cp arch/i386/boot/bzImage
/boot/vmlinuz−2.2.16
mkinitrd /boot/initrd−2.2.16.img 2.2.16
vi /etc/lilo.conf
lilo
vi /etc/system
reboot
doconfig
List modules genkex kldstat kmadmin −s lsmod modinfo
Load module kldload kmadmin −L insmod modload
Unload module kldunload kmadmin −U rmmod modunload
Initialize system install_assist /stand/sysinstall set_parms initial netconf sys−unconfig netsetup
Physical RAM bootinfo −r sysctl hw.physmem
grep −i Physical
/var/adm/syslog/syslog.log
free prtconf uerf grep memory
Kernel Bits bootinfo −k getconf KERNEL_BITS getconf WORD_BIT isainfo −kv 64
Crash utility crash crash adb lcrash crash kdbx
Trace System Calls syscalls truss tusc strace truss trace
Machine model
uname −m
bootinfo −m
uname −m
model
uname −m
uname −m uname −imp uname −p
OS Level oslevel uname −r uname −r uname −r uname −r sizer −v
Run Level who −r who −r runlevel who −r who −r
Core dump files /var/adm/ras /var/adm/crash /var/crash/`uname −n`
Boot single user
Key on service mode/F4
Boot from CD/Tape
Select Maintenance
Limited function Shell
ok boot −s
>boot
Interact with IPL ? Y
ISL>hpux −iS
{lilo}
control−x
linux S
{grub}
c
kernel vmlinuz−2.4.9−13 single
ro root=/dev/hda8
initrd /initrd−2.4.9−13.img
boot
ok boot −s >>> boot −fl s
Maintenance mode ok boot −as
>boot
Interact with IPL ? Y
ISL>hpux −lm
ok boot −as
Interrupt Key control−B Stop−A control−P
Return to console co ok go
Timezone Management
/etc/environment
/etc/profile
/etc/localtime /etc/TIMEZONE /etc/sysconfig/clock
/etc/TIMEZONE
/etc/default/init
/etc/svid3_tz
timezone
NTP Daemon
/etc/ntp.conf
startsrc −s xntpd
/etc/rc.conf
{xntpd_enable="YES"}
/etc/rc.network
/etc/rc.config.d/netdaemons
/sbin/init.d/xntpd
/etc/ntp.conf
/etc/rc.d/init.d/xntpd
/etc/inet/ntp.conf
/etc/init.d/xntpd
rcmgr set XNTPD_CONF YES
/sbin/init.d/xntpd
Software AIX HP−UX LINUX(RedHat) SOLARIS Tru64
Install Software installp −a pkg_add swinstall rpm −i package pkgadd setld −l
Uninstall software installp −u pkg_delete swremove rpm −e package pkgrm setld −d
List installed
software
lslpp −L all pkg_info −a swlist rpm −qa pkginfo setld −i
Verify installed
software
lppchk −v swlist −l fileset −a state rpm −V package
pkginfo −i
pkginfo −p
setld −v
List all files lslpp −f fileset pkg_info −L package swlist −l file fileset rpm −ql package pkgchk −l package setld −i package
List installed
patches
instfix −i
swlist −l patch
what /stand/vmunix
patchadd −p
dupatch −track −type
patch
Package owner lslpp −w path swlist −l file grep path rpm −qf file pkgchk −l −p path
SW Directory /usr/lpp /var/db/pkg /var/adm/sw/ /var/lib/rpm /var/sadm /var/adm/smlogs
Devices AIX FreeBSD HP−UX LINUX(RedHat) SOLARIS Tru64
Devices /dev /dev /dev /dev /devices /dev
Install devices for
attached peripherals
cfgmgr −v /dev/MAKEDEV insf −e /dev/MAKEDEV
drvconfig
devlinks
disks
tapes
ports
scu scan edt
scsimgr −scan_all
Remove device rmdev −l rmsf rem_drv
Device drivers lscfg lsdev prtconf −D
CPU lsdev −Cc processor sysctl hw.model ioscan −fnC processor cat /proc/cpuinfo psrinfo −v psrinfo −v
List Terminal lsdev −Cc tty ioscan −fnC tty pmadm −l
Diagnostics diag pciconf −l stm
/usr/platform/`uname −m`/
sbin/prtdiag
ok test−all
/opt/SUNWvts/bin/sunvts
Whole Disk /dev/hdisk# /dev/ad0s1c /dev/dsk/c#t#d0 /dev/sda /dev/c#t#d0s2 /dev/rz0c
CDROM /dev/cd0 /dev/acd0c /dev/dsk/c#t2d0 /dev/cdrom /dev/dsk/c#t6d0s2 /dev/rz3c
CDROM file type cdrfs cd9660 cdfs iso9660 hsfs cdfs
Rewinding tape drive /dev/rmt0 /dev/rwt0d /dev/rmt/0m /dev/rst0 { c 9 0} /dev/rmt/0 /dev/rmt0
Non−rewinding tape
drive
/dev/rmt0.1 /dev/nrwt0d /dev/rmt/0mn /dev/nrst0 { c 9 128 } /dev/rmt/0n /dev/nrmt0
Floppy drive /dev/rfd0 /dev/fd0 − /dev/fd0 /dev/diskette /dev/fd0c
Links AIX FreeBSD HP−UX LINUX(RedHat) SOLARIS Tru64
FAQ AIX−FAQ FreeBSD FAQ HP−UX FAQ LINUX FAQ Solaris 2 FAQ Tru64 FAQ
Online Manual AIX 4.3 Books FreeBSD Hand Book HP−UX 11.00 Collection Linux Documentation Project Solaris 7 Documentation Tru64 Documents
Technical Support RS/6000 TechSupport IT Resource Center Red Hat support SunSolve Alpha Systems Support
Phone Number 1−800−CALL−AIX 1−800−633−3600 1−888−REDHAT1 1−800−USA−4SUN
Free Software Bull FreeBSD Primary Site HP−UX Ports Linux Software Map Sun Freeware
Tru64 Demos, Shareware &
Freeware
Certification www.ibm.com education.hp.com RHCE suned.sun.com ASE Information
Directory Mappings AIX FreeBSD HP−UX LINUX(RedHat) SOLARIS Tru64
Root filesystem / {/dev/hd4} / {/dev/ad0s1a} / {/dev/vg00/lvol1} / {/dev/sda1} / {/dev/vx/dsk/rootvol} / {/dev/rz0a}
Home Directory /home {/dev/hd1} /home {/dev/vg00/lvol4}
/export/home
/dev/vx/dsk/home}
/tmp {/dev/hd3} /tmp {/dev/vg00/lvol6}
/tmp
/dev/vx/dsk/swapvol}
/usr {/dev/hd2} /usr {/dev/ad0s1f} /usr {/dev/vg00/lvol7} /usr /usr {/dev/rz0g}
/var {/dev/hd9var} /var {/dev/ad0s1e} /var {/dev/vg00/lvol8} /var
Sample configuration
files
− /usr/newconfig
User Accounts AIX FreeBSD HP−UX LINUX(RedHat) Solaris Tru64
Password files
/etc/passwd
/etc/security/passwd
/etc/passwd
/etc/master.passwd
/etc/passwd
/tcb/files/auth/r/root
/etc/passwd
/etc/shadow
/etc/passwd
/etc/shadow
/etc/passwd
Groups file
/etc/group
/etc/security/group
/etc/group
/etc/group
/etc/logingroup
/etc/group /etc/group /etc/group
Maximum # of user ID 4294967295 65535 2147483647 65535 2147483647 65535
Allow/Deny remote
login
/etc/security/user
{rlogin=true}
/etc/ttys
{secure}
/etc/securetty
{console}
/etc/securetty
{ttyp1}
/etc/default/login
{CONSOLE=/dev/console}
/etc/securettys
{ttyp1}
User nobody's id # 4294967294 65534 −2 99 60001 & 65534(nobody4) 65534
Group nobody's id # 4294967294 65534 −2(nogroup) 99 60002 & 65534(nogroup) 65534
Recover root
password
boot from CD/Tape
Installation/Maintenance
Start Limited Shell
getrootfs hdisk0
vi /etc/security/passwd
ok boot −s
passwd root
>boot
Interact with IPL ? Y
ISL>hpux −iS
passwd root
{lilo}
control−x
linux S
passwd root
{grub}
c
kernel vmlinuz−2.4.9−13 single
ro root=/dev/hda8
initrd /initrd−2.4.9−13.img
boot
passwd root
boot cdrom −s
mkdir /tmp/a
mount /dev/c0t0d0s0
/tmp/a
vi /tmp/a/etc/shadow
press the HALT Button or
(Control−P)
>>>boot −fl s
lsmbstartup
/sbin/bcheckrc
passwd root
Create new user mkuser adduser useradd useradd useradd useradd
Delete user rmuser rmuser userdel userdel userdel userdel
List users lsuser −f ALL logins logins
Modify user account chuser −a usermod usermod usermod usermod
General Commands AIX FreeBSD HP−UX LINUX(RedHat) Solaris Tru64
Unique host ID hostid uname −i hostid hostid hostid
Administrator smit sam linuxconf admintool
Performance monitor
top
monitor
top
top
glance
top top top
System activity
reporter
sar sa sar sar {sysstat} sar /usr/opt/svr4/bin/sar
Virtual Memory
statistics
vmstat vmstat vmstat vmstat vmstat vmstat
I/O statistics iostat iostat iostat iostat {sysstat} iostat iostat
Error logs
alog −o −t boot
errpt
dmesg dmesg dmesg dmesg uerf −R −o full
Physical RAM 1TB 4TB 64 GB {>2.3.24} 16TB 4TB
Shared Memory 2.75GB 8TB sysctl kernel.shmmax
Process Data Space 2GB 4GB 900 MB
Swap device /dev/hd6 /dev/ad0s1b /dev/vg00/lvol2 /dev/sda2 /dev/vx/dsk/swapvol /dev/rz0b
Swap file type /etc/swapspaces swap swap partition type 82 swap raw
Display swap size lsps −a swapinfo swapinfo −a free swap −l swapon −s
Activate Swap swapon −a swapon −a swapon −a swapon −a swap −a swapon −a
Printers AIX FreeBSD HP−UX LINUX Solaris Tru64
Printer Queues /etc/qconfig /var/spool/print /etc/lp/interface/* /var/spool/lpd/lp/* /etc/lp/interfaces/* /usr/spool/lpd
Stop LP stopsrc −s lpd lpshut /etc/init.d/lpd stop /usr/lib/lp/lpshut /sbin/init.d/lpd stop
Start LP startsrc −s lpd lpd lpsched /etc/init.d/lpd start /usr/lib/lp/lpsched /sbin/init.d/lpd start
Submit print jobs
enq
lp
lpr
qprt
lp lp lpr
lp
lpr
lp
lpr
LP statistics
enq −A
lpq
lpstat
qchk
lpq lpstat lpq lpstat lpstat
Remove print jobs
cancel
lprm
qcan
enq −x
cancel
lprm
cancel lprm
cancel
lprm
cancel
lprm
Add printer queue smit mkpq lpadmin −p pq printtool lpadmin −p pq lprsetup
Remove Printer queue smit rmpq lpadmin −x pq lpadmin −x pq lprsetup
Make default printer export LPDEST="pq" lpadmin −d pq lpadmin −d pq export PRINTER="lp"
TCP/IP AIX HP−UX LINUX(RedHat) Solaris Tru64
Network IP
configuration
lsattr −E −l inet0 /etc/rc.conf /etc/rc.config.d/netconf /etc/sysconfig/network−scripts/
/etc/hostname.*
/etc/inet/*
/etc/defaultrouter
/etc/rc.config
Hosts IP addresses /etc/hosts /etc/hosts /etc/hosts /etc/hosts /etc/inet/hosts /etc/hosts
Name service switch /etc/netsvc.conf /etc/host.conf /etc/nsswitch.conf /etc/nsswitch.conf /etc/nsswitch.conf /etc/svc.conf
Network parameters no −a sysctl ndd −h sysctl −a grep net ndd /dev/[tcpip] ?
Routing daemon gated routed gated routed in.routed routed
NIC Configurations ifconfig −a ifconfig −a lanscan −v ifconfig −a ifconfig −a ifconfig −a
Secondary IP Address ifconfig en0 alias IP ifconfig xl0 alias IP ifconfig lan0:1 IP
modprobe ip_alias
ifconfig eth0:1 IP
ifconfig hme0:1 IP up ifconfig ln0 alias
Login prompt
HERALD @
/etc/security/login.cfg
telnetd −b /etc/issue /etc/issue
BANNER @
/etc/default/telnetd
/etc/issue
Increase the # of
pseudo−terminals
odmget −q "attribute=num
and
uniquetype=pty/pty/pty"
PdAt sed "s/0−64/0−512/"
odmchange −q
"attribute=num and
uniquetype=pty/pty/pty"
−o PdAt
chdev −l pty0 −anum=256 −P
reboot
rebuild your kernel with these
new values NPTY=#
NSTRPY=#
reboot
insf −d ptys −n #
insf −d ptym −n #
insf −d pts −s # −e −v
cd /dev
./MAKEDEV −v pty
{/etc/system}
set pt_cnt = # {SYSV}
set npty = # {BSD}
{/etc/iu.ap}
ptsl 0 # ldterm ttcompat
halt
boot −r
cd /dev
./MAKEDEV PTY_1
Maximum # of ptys 512 {MAXUSERS} 256
176 {BSD}
3000 {SYSV}
8192
Remote Shell
remsh
rsh
rsh remsh rsh rsh rsh
YP/NIS service
binder
/usr/lib/netsvc/yp/ypbind /usr/sbin/ypbind /usr/lib/netsvc/yp/ypbind /sbin/ypbind /usr/lib/netsvc/yp/ypbind /usr/sbin/ypbind
System Files AIX FreeBSD HP−UX LINUX(RedHat) Solaris Tru64
NFS exported /etc/exports /etc/exports /etc/exports /etc/exports
/etc/dfs/dfstab
/etc/dfs/sharetab
/etc/exports
NFS Client mounted
directories
/etc/xtab /etc/xtab /var/lib/nfs/xtab /etc/rmtab /var/adm/mountdtab
Max File System 128 GB 128 GB 2 TB
1 TB
8000 TB {vxfs}
128 GB {<= 3.2G}
512 GB {>= 4.0}
16 TB {advfs}
Max File Size 64 GB 128 GB
2 GB {512B block size}
8192 GB {8KB block size}
1 TB
2 GB {=
128 GB {<= 3.2G}
512 GB {>= 4.0}
16 TB {advfs}
Max # File
Descriptors
64 K 60~ K sysctl fs.file−max 64 K 64 K
DISK/LVM Commands AIX FreeBSD HP−UX:Disk &Filesystem LINUX(RedHat) SOLARIS Tru64
Filesystem table /etc/filesystems /etc/fstab /etc/fstab /etc/fstab /etc/vfstab /etc/fstab
Free disk blocks df −k df −k bdf df −k df −k df −k
Device listing lsdev −C /sbin/ioscan cat /proc/devices sysdef
Disk information bootinfo −s hdisk# fdisk −v ad0 diskinfo /dev/rdsk/c#t#d# cat /proc/scsi/scsi0/sda/model
format −d c#t#d#
format>current
format>inquiry
file /dev/rrz0c
Disk Label lspv −l hdisk# disklabel ad0 pvdisplay −v /dev/dsk/C#t#d# fdisk −l prtvtoc disklabel −p rz0
LVM Concepts Partition sub disk logical extents logical extents sub disk sub disk
Volume Volume logical volume logical volume Volume Volume
Plex Plex Plex
Volume group volume group volume group disk group disk group
Journal Filesystem
type
jfs vxfs ext2 vxfs advfs
Default volume group /dev/rootvg /dev/vg00 /dev/vx/dsk/rootdg /dev/vol/rootdg
Display volume group lsvg −l rootvg vgdisplay −v vg00 vgdisplay −v vxprint −l −g rootdg volprint −l −g rootdg
Modify physical
volume
chpv pvchange pvchange
Prepare physical
disk
mkdev −c disk −l hdisk# pvcreate pvcreate vxdiskadd voldiskadd
List physical volume lspv vinum ld pvdisplay pvdisplay vxprint −dl volprint −dl
Remove disk from
volume group
reducevg vgreduce vgreduce vxdg rmdisk voldg rmdisk
Move logical volumes
to another physical
volumes
migratepv
vinum move −f drive
object
pvmove pvmove vxassist move volassist move
Create volume group mkvg vgcreate vgcreate vxdg init voldg init
Remove volume group vgremove vgremove
Volume group
availability
chvg
varyonvg
varyoffvg
vgchange vgchange
Restore volume group vgcfgrestore vgcfgrestore
Exports volume group exportvg vgexport vgexport vxdg deport voldg deport
Imports volume group importvg vgimport vgimport vxdg import voldg import
Volume group listing lsvg vgscan vgscan
Change logical
volume
characteristics
chlv lvchange lvchange vxedit set voledit set
List logical volume lslv vinum lv lvdisplay lvdisplay vxprint −vl volprint −vl
Make logical volume mklv lvcreate lvcreate vxassist make volassist make
Extend logical
volume
extendlv lvextend lvextend vxassist growto volassist growto
Reduce logical
volume
AIX reduce LV lvreduce lvreduce vxassist shrinkto volassist shrinkto
Remove logical
volume
rmlv vinum rm vol lvremove lvremove vxedit rm
voledit −g rootdg −rf rm
vol1
Prepare boot volumes bootlist −m normal lvlnboot lilo vxbootsetup
Remove boot volumes lvrmboot
Extend File system chfs −a size=# /mt
extendfs /dev/vg00/lvol8
fsadm −F vxfs −b {LE * 1024} /mt
resize2fs
vxva
mkfs −M
Reduce/Split mirrors rmlvcopy lvsplit lvsplit
Merge mirrors lvmerge lvmerge
Create mirrors mklv −c 2 vinum mirror drive lvcreate −m 1 vxassist mirror
volassist make vol 100mb
mirror=true
Add mirrors mklvcopy lv 2 lvextend −m 1
Create striped
volumes
mklv −u 3 −S 64K vinum stripe drive lvcreate −i 3 −I 64 lvcreate −i 3 −I 64
vxassist make vol 100mb
layout=raid5
volassist make vol 100mb
layout=stripe
System recovery tape mksysb −i /dev/rmt0 /opt/ignite/bin/make_recovery /usr/sys/bin/btcreate
Backup savevg −i rootvg vinum saveconfig fbackup tar cvf /dev/rst0 / ufsdump vdump
Restore restvg frecover tar xvf /dev/rst0 ufsrestore vrestore
MISC AIX FreeBSD HP−UX LINUX(RedHat) SOLARIS Tru64
Startup script /etc/rc /etc/rc /sbin/rc /etc/rc.d/rc /sbin/init.d /sbin/init.d
Kernel /usr/lib/boot/unix_up /kernel /stand/vmunix /boot/vmlinuz /kernel/genunix /vmunix
Kernel Parameters lsattr −E −l sys0 sysctl −a
sysdef
kmtune
kmsystem
sysctl −a sysdef −i
sysconfig
dxkerneltuner
Reconfigure the
kernel chdev −l sys0 −a
cd /sys/i386/conf
vi KERNEL
config KERNEL
cd ../../compile/KERNEL
make depend
make
make install
cd /stand/build
/usr/lbin/sysadm/system_prep −v
−s system
vi system
mk_kernel −s system
cd /stand
mv system system.prev
mv vmunix vmunix.prev
mv dlkm dlkm.prev
mv /stand/build/system system
kmupdate /stand/build/vmunix_test
cd /usr/src/linux
make mrproper
make menuconfig
make dep
make clean
make bzimage
make install
make modules
make modules_install
cp arch/i386/boot/bzImage
/boot/vmlinuz−2.2.16
mkinitrd /boot/initrd−2.2.16.img 2.2.16
vi /etc/lilo.conf
lilo
vi /etc/system
reboot
doconfig
List modules genkex kldstat kmadmin −s lsmod modinfo
Load module kldload kmadmin −L insmod modload
Unload module kldunload kmadmin −U rmmod modunload
Initialize system install_assist /stand/sysinstall set_parms initial netconf sys−unconfig netsetup
Physical RAM bootinfo −r sysctl hw.physmem
grep −i Physical
/var/adm/syslog/syslog.log
free prtconf uerf grep memory
Kernel Bits bootinfo −k getconf KERNEL_BITS getconf WORD_BIT isainfo −kv 64
Crash utility crash crash adb lcrash crash kdbx
Trace System Calls syscalls truss tusc strace truss trace
Machine model
uname −m
bootinfo −m
uname −m
model
uname −m
uname −m uname −imp uname −p
OS Level oslevel uname −r uname −r uname −r uname −r sizer −v
Run Level who −r who −r runlevel who −r who −r
Core dump files /var/adm/ras /var/adm/crash /var/crash/`uname −n`
Boot single user
Key on service mode/F4
Boot from CD/Tape
Select Maintenance
Limited function Shell
ok boot −s
>boot
Interact with IPL ? Y
ISL>hpux −iS
{lilo}
control−x
linux S
{grub}
c
kernel vmlinuz−2.4.9−13 single
ro root=/dev/hda8
initrd /initrd−2.4.9−13.img
boot
ok boot −s >>> boot −fl s
Maintenance mode ok boot −as
>boot
Interact with IPL ? Y
ISL>hpux −lm
ok boot −as
Interrupt Key control−B Stop−A control−P
Return to console co ok go
Timezone Management
/etc/environment
/etc/profile
/etc/localtime /etc/TIMEZONE /etc/sysconfig/clock
/etc/TIMEZONE
/etc/default/init
/etc/svid3_tz
timezone
NTP Daemon
/etc/ntp.conf
startsrc −s xntpd
/etc/rc.conf
{xntpd_enable="YES"}
/etc/rc.network
/etc/rc.config.d/netdaemons
/sbin/init.d/xntpd
/etc/ntp.conf
/etc/rc.d/init.d/xntpd
/etc/inet/ntp.conf
/etc/init.d/xntpd
rcmgr set XNTPD_CONF YES
/sbin/init.d/xntpd
Software AIX HP−UX LINUX(RedHat) SOLARIS Tru64
Install Software installp −a pkg_add swinstall rpm −i package pkgadd setld −l
Uninstall software installp −u pkg_delete swremove rpm −e package pkgrm setld −d
List installed
software
lslpp −L all pkg_info −a swlist rpm −qa pkginfo setld −i
Verify installed
software
lppchk −v swlist −l fileset −a state rpm −V package
pkginfo −i
pkginfo −p
setld −v
List all files lslpp −f fileset pkg_info −L package swlist −l file fileset rpm −ql package pkgchk −l package setld −i package
List installed
patches
instfix −i
swlist −l patch
what /stand/vmunix
patchadd −p
dupatch −track −type
patch
Package owner lslpp −w path swlist −l file grep path rpm −qf file pkgchk −l −p path
SW Directory /usr/lpp /var/db/pkg /var/adm/sw/ /var/lib/rpm /var/sadm /var/adm/smlogs
Devices AIX FreeBSD HP−UX LINUX(RedHat) SOLARIS Tru64
Devices /dev /dev /dev /dev /devices /dev
Install devices for
attached peripherals
cfgmgr −v /dev/MAKEDEV insf −e /dev/MAKEDEV
drvconfig
devlinks
disks
tapes
ports
scu scan edt
scsimgr −scan_all
Remove device rmdev −l rmsf rem_drv
Device drivers lscfg lsdev prtconf −D
CPU lsdev −Cc processor sysctl hw.model ioscan −fnC processor cat /proc/cpuinfo psrinfo −v psrinfo −v
List Terminal lsdev −Cc tty ioscan −fnC tty pmadm −l
Diagnostics diag pciconf −l stm
/usr/platform/`uname −m`/
sbin/prtdiag
ok test−all
/opt/SUNWvts/bin/sunvts
Whole Disk /dev/hdisk# /dev/ad0s1c /dev/dsk/c#t#d0 /dev/sda /dev/c#t#d0s2 /dev/rz0c
CDROM /dev/cd0 /dev/acd0c /dev/dsk/c#t2d0 /dev/cdrom /dev/dsk/c#t6d0s2 /dev/rz3c
CDROM file type cdrfs cd9660 cdfs iso9660 hsfs cdfs
Rewinding tape drive /dev/rmt0 /dev/rwt0d /dev/rmt/0m /dev/rst0 { c 9 0} /dev/rmt/0 /dev/rmt0
Non−rewinding tape
drive
/dev/rmt0.1 /dev/nrwt0d /dev/rmt/0mn /dev/nrst0 { c 9 128 } /dev/rmt/0n /dev/nrmt0
Floppy drive /dev/rfd0 /dev/fd0 − /dev/fd0 /dev/diskette /dev/fd0c
Links AIX FreeBSD HP−UX LINUX(RedHat) SOLARIS Tru64
FAQ AIX−FAQ FreeBSD FAQ HP−UX FAQ LINUX FAQ Solaris 2 FAQ Tru64 FAQ
Online Manual AIX 4.3 Books FreeBSD Hand Book HP−UX 11.00 Collection Linux Documentation Project Solaris 7 Documentation Tru64 Documents
Technical Support RS/6000 TechSupport IT Resource Center Red Hat support SunSolve Alpha Systems Support
Phone Number 1−800−CALL−AIX 1−800−633−3600 1−888−REDHAT1 1−800−USA−4SUN
Free Software Bull FreeBSD Primary Site HP−UX Ports Linux Software Map Sun Freeware
Tru64 Demos, Shareware &
Freeware
Certification www.ibm.com education.hp.com RHCE suned.sun.com ASE Information
FW: J2EE Addin parameters missing in the profile, j2ee no longer starts
J2EE Addin parameters missing in the profile, j2ee no longer starts
Symptom
The profile parameters that you create when installing the J2EE engine are lost.
You can no longer start the J2EE engine.
Other terms
RZ10, profile maintenance
Reason and Prerequisites
In the standard J2EE installation, additional profile parameters are only saved in the operating system files. The parameters do not exist in the TPFHT and TPFET tables. The online profile maintenance (Transaction RZ10 and Transaction RZ11) edits tables TPFHT and TPFET, and generates a copy of the parameters in the operating system files when you activate the profile for the first time. The operating system files are then interpreted when you start the SAP System, and the resources are created in the defined size. During the activation in Transaction RZ10, the old operating system files are protected from being overwritten ('*.BAK') so that you can restore the previous version if necessary.
Solution
You must maintain the J2EE parameters in Transaction RZ10. You can retrieve the parameters that are generated automatically from the backup copy of the operating system file. You can display the saved file with Transaction AL11 or with a suitable editor on operating system level.
COMPARE:
------------
Use the comparison function in Transaction RZ10 to identify parameters that are inconsistent between the operating system file and the online tables. You can activate the function in the 'Profile' menu:
'Profile -> Comparisons -> Profile in database -> Against active profile'
IMPORT:
------------
Use the import function to import the parameters of the operating system files into the online tables. You can activate the import in the 'Profile' menu in Transaction RZ10:
'Profile -> Import'
Refer to the online documentation for more information.
For J2EE Engine 6.30/6.40, you must maintain the following parameters in the instance profile:
exe/j2ee = $(DIR_INSTANCE)/j2ee/os_libs/jcontrol.exe
rdisp/j2ee_start_control = 1
rdisp/j2ee_start = 1
rdisp/j2ee_timeout = 600
rdisp/frfc_fallback = on
jstartup/trimming_properties = off
jstartup/protocol = on
exe/jlaunch = $(DIR_INSTANCE)/j2ee/os_libs/jlaunch.exe
jstartup/instance_properties = $(INSTANCE_PROPERTIES);$(SDM_PROPERTIES)
ms/server_port_0 = PROT=HTTP, PORT=81
INSTANCE_PROPERTIES = $(DIR_INSTANCE)/j2ee/cluster/instance.properties SDM_PROPERTIES = $(DIR_INSTANCE)/SDM/program/config/sdm_jstartup.properties
icm/HTTP/j2ee_0 = PREFIX=/,HOST=,CONN=0-500,PORT=
For NetWeaver 2004s
the following parameters must be maintained in the instance profile:
jstartup/trimming_properties = off
jstartup/vm/home =
jstartup/max_caches = 500
jstartup/release = 700
jstartup/instance_properties = $(jstartup/j2ee_properties);$(jstartup/sdm_properties) //path separator is OS dependent
j2ee/dbdriver = // path separator is OS dependent
j2ee/instance_id =
jstartup/protocol = on
rdisp/j2ee_start_control = 1
rdisp/j2ee_start = 1
rdisp/j2ee_libpath = $(DIR_EXECUTABLE)
exe/j2ee = $(DIR_EXECUTABLE)/jcontrol$(FT_EXE)
rdisp/j2ee_timeout = 600
rdisp/frfc_fallback = on
icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00
icm/server_port_0 = PROT=HTTP,PORT=80$$
Note that the above example applies to Windows platforms and the ".exe" extension must be removed for other platforms.
Symptom
The profile parameters that you create when installing the J2EE engine are lost.
You can no longer start the J2EE engine.
Other terms
RZ10, profile maintenance
Reason and Prerequisites
In the standard J2EE installation, additional profile parameters are only saved in the operating system files. The parameters do not exist in the TPFHT and TPFET tables. The online profile maintenance (Transaction RZ10 and Transaction RZ11) edits tables TPFHT and TPFET, and generates a copy of the parameters in the operating system files when you activate the profile for the first time. The operating system files are then interpreted when you start the SAP System, and the resources are created in the defined size. During the activation in Transaction RZ10, the old operating system files are protected from being overwritten ('*.BAK') so that you can restore the previous version if necessary.
Solution
You must maintain the J2EE parameters in Transaction RZ10. You can retrieve the parameters that are generated automatically from the backup copy of the operating system file. You can display the saved file with Transaction AL11 or with a suitable editor on operating system level.
COMPARE:
------------
Use the comparison function in Transaction RZ10 to identify parameters that are inconsistent between the operating system file and the online tables. You can activate the function in the 'Profile' menu:
'Profile -> Comparisons -> Profile in database -> Against active profile'
IMPORT:
------------
Use the import function to import the parameters of the operating system files into the online tables. You can activate the import in the 'Profile' menu in Transaction RZ10:
'Profile -> Import'
Refer to the online documentation for more information.
For J2EE Engine 6.30/6.40, you must maintain the following parameters in the instance profile:
exe/j2ee = $(DIR_INSTANCE)/j2ee/os_libs/jcontrol.exe
rdisp/j2ee_start_control = 1
rdisp/j2ee_start = 1
rdisp/j2ee_timeout = 600
rdisp/frfc_fallback = on
jstartup/trimming_properties = off
jstartup/protocol = on
exe/jlaunch = $(DIR_INSTANCE)/j2ee/os_libs/jlaunch.exe
jstartup/instance_properties = $(INSTANCE_PROPERTIES);$(SDM_PROPERTIES)
ms/server_port_0 = PROT=HTTP, PORT=81
INSTANCE_PROPERTIES = $(DIR_INSTANCE)/j2ee/cluster/instance.properties SDM_PROPERTIES = $(DIR_INSTANCE)/SDM/program/config/sdm_jstartup.properties
icm/HTTP/j2ee_0 = PREFIX=/,HOST=
For NetWeaver 2004s
the following parameters must be maintained in the instance profile:
jstartup/trimming_properties = off
jstartup/vm/home =
jstartup/max_caches = 500
jstartup/release = 700
jstartup/instance_properties = $(jstartup/j2ee_properties);$(jstartup/sdm_properties) //path separator is OS dependent
j2ee/dbdriver =
j2ee/instance_id =
jstartup/protocol = on
rdisp/j2ee_start_control = 1
rdisp/j2ee_start = 1
rdisp/j2ee_libpath = $(DIR_EXECUTABLE)
exe/j2ee = $(DIR_EXECUTABLE)/jcontrol$(FT_EXE)
rdisp/j2ee_timeout = 600
rdisp/frfc_fallback = on
icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00
icm/server_port_0 = PROT=HTTP,PORT=80$$
Note that the above example applies to Windows platforms and the ".exe" extension must be removed for other platforms.
How to Check Windows is 32 or 64 bit
This step-by-step article describes how to determine whether a computer is running a 32-bit Microsoft Windows operating system or a 64-bit Microsoft Windows operating system. To determine whether your computer is running a 32-bit Windows operating system or a 64-bit Windows operating system, examine the system information. To do this, use one of the following methods. Note Intel Itanium-based computers can only run 64-bit versions of Windows. Intel Itanium-based computers cannot run a 32-bit Windows operating system. Currently, 64-bit Versions of Windows only run on Itanium-based computers.
Use My Computer to Check System Properties
1.
Click Start, right-click My Computer, and then click Properties.
2.
In the System Properties window, click the General tab.
3.
Note the first line under Computer:
•
On 64-bit systems, Itanium or Itanium 2 appears on this line.
•
On 32-bit systems, a value other than Itanium or Itanium2 appears on this line.
Use the Winmsd.exe Tool to Check the System Type
1.
Click Start, and then click Run.
2.
Type winmsd.exe in the Open box, and then click OK.
3.
Locate System Type in the right pane under Item. Note the value.
•
If the value that corresponds to System Type is X86-based PC, the computer is running a 32-bit version of the Windows operating system.
•
If the value that corresponds to System Type is Itanium–based system, the computer is running a 64-bit version of the Windows operating system.
Use the Winmsd.exe Tool to Check the Processor
1.
Click Start, and then click Run.
2.
Type winmsd.exe in the Open box, and then click OK.
3.
Locate Processor in the right pane under Item. Note the value.
•
If the value that corresponds to Processor starts with x86, the computer is running a 32-bit version of the Windows operating system.
•
If the value that corresponds to Processor starts with ia64, the computer is running a 64-bit version of the Windows operating system.
Use My Computer to Check System Properties
1.
Click Start, right-click My Computer, and then click Properties.
2.
In the System Properties window, click the General tab.
3.
Note the first line under Computer:
•
On 64-bit systems, Itanium or Itanium 2 appears on this line.
•
On 32-bit systems, a value other than Itanium or Itanium2 appears on this line.
Use the Winmsd.exe Tool to Check the System Type
1.
Click Start, and then click Run.
2.
Type winmsd.exe in the Open box, and then click OK.
3.
Locate System Type in the right pane under Item. Note the value.
•
If the value that corresponds to System Type is X86-based PC, the computer is running a 32-bit version of the Windows operating system.
•
If the value that corresponds to System Type is Itanium–based system, the computer is running a 64-bit version of the Windows operating system.
Use the Winmsd.exe Tool to Check the Processor
1.
Click Start, and then click Run.
2.
Type winmsd.exe in the Open box, and then click OK.
3.
Locate Processor in the right pane under Item. Note the value.
•
If the value that corresponds to Processor starts with x86, the computer is running a 32-bit version of the Windows operating system.
•
If the value that corresponds to Processor starts with ia64, the computer is running a 64-bit version of the Windows operating system.
Bex clnt server tech
we have had several customer messages facing problems with Bex Web Analyzer within a portal environment and message server used for load distribution.
The problem itself is related to the fact that the message server is sending a 301 redirect instead of 307 redirect and therefore the POST header fields get lost. This leads to an empty Bex Web Analyzer.
The problem can be resolved by setting "ms/redirect_version = 1" .
Further informations can be found in the following notes :
BW-BEX-ET-BC :
https://websmp230.sap-ag.de/sap/bc/bsp/spn/sapnotes/index2.htm?numm=972514
BC-CST-MS:
https://websmp230.sap-ag.de/sap/bc/bsp/spn/sapnotes/index2.htm?numm=857596
https://websmp230.sap-ag.de/sap/bc/bsp/spn/sapnotes/index2.htm?numm=1055324
The problem itself is related to the fact that the message server is sending a 301 redirect instead of 307 redirect and therefore the POST header fields get lost. This leads to an empty Bex Web Analyzer.
The problem can be resolved by setting "ms/redirect_version = 1" .
Further informations can be found in the following notes :
BW-BEX-ET-BC :
https://websmp230.sap-ag.de/sap/bc/bsp/spn/sapnotes/index2.htm?numm=972514
BC-CST-MS:
https://websmp230.sap-ag.de/sap/bc/bsp/spn/sapnotes/index2.htm?numm=857596
https://websmp230.sap-ag.de/sap/bc/bsp/spn/sapnotes/index2.htm?numm=1055324
MCOD sripts
This script is for adding the database user with the proper security.
Replace SID with yourSID
replace sid with your sid.
1. use master
EXEC sp_addlogin 'sid', 'mss123', 'SID'
go
use SID
EXEC sp_grantdbaccess 'sid'
EXEC sp_addrolemember 'db_owner', 'sid'
go
use master
EXEC sp_grantdbaccess 'sid'
EXEC sp_addrolemember 'db_owner', 'sid'
go
use msdb
EXEC sp_grantdbaccess 'sid'
EXEC sp_addrolemember 'db_owner', 'sid'
EXEC sp_addrolemember 'TargetServersRole', 'sid'
go
use model
EXEC sp_grantdbaccess 'sid'
EXEC sp_addrolemember 'db_owner', 'sid'
go
use tempdb
EXEC sp_grantdbaccess 'sid'
EXEC sp_addrolemember 'db_owner', 'sid'
go
use master
grant all on xp_cmdshell to sid
go
EXEC sp_addsrvrolemember 'sid', 'serveradmin'
EXEC sp_addsrvrolemember 'sid', 'dbcreator'
EXEC sp_addsrvrolemember 'sid', 'bulkadmin'
go
Following script will create the procedure for changing owner ship.
Just change the SID with ur sid.
2. use SID
go
if object_id('sp_change_sapuser') is not null
drop procedure sp_change_sapuser
go
create procedure sp_change_sapuser @oldid sysname, @newid sysname
as begin
declare @oldid_uid smallint
declare @newid_uid smallint
declare @object sysname
declare @object_full nvarchar(999)
set @oldid_uid = user_id(@oldid)
set @newid_uid = user_id(@newid)
if @oldid_uid is not null and @newid_uid is not null
begin
declare object_cursor cursor local for
select name
from sysobjects
where xtype in ('U', 'V', 'P', 'D')
and name not in ('syssegments','sysconstraints')
and @oldid_uid = uid
open object_cursor
fetch next from object_cursor into @object
while @@fetch_status=0
begin
set @object_full = user_name(@oldid_uid) + '.' + @object
exec sp_changeobjectowner @object_full, @newid
fetch next from object_cursor into @object
end
end
else
if @oldid_uid is null
begin
print '*** old database user does not exist ***'
end
if @newid_uid is null
begin
print '*** new database user does not exist ***'
end
end
executing above created procedure.,
3. exec sp_change_sapuser 'dbo', 'sid'
Replace SID with yourSID
replace sid with your sid.
1. use master
EXEC sp_addlogin 'sid', 'mss123', 'SID'
go
use SID
EXEC sp_grantdbaccess 'sid'
EXEC sp_addrolemember 'db_owner', 'sid'
go
use master
EXEC sp_grantdbaccess 'sid'
EXEC sp_addrolemember 'db_owner', 'sid'
go
use msdb
EXEC sp_grantdbaccess 'sid'
EXEC sp_addrolemember 'db_owner', 'sid'
EXEC sp_addrolemember 'TargetServersRole', 'sid'
go
use model
EXEC sp_grantdbaccess 'sid'
EXEC sp_addrolemember 'db_owner', 'sid'
go
use tempdb
EXEC sp_grantdbaccess 'sid'
EXEC sp_addrolemember 'db_owner', 'sid'
go
use master
grant all on xp_cmdshell to sid
go
EXEC sp_addsrvrolemember 'sid', 'serveradmin'
EXEC sp_addsrvrolemember 'sid', 'dbcreator'
EXEC sp_addsrvrolemember 'sid', 'bulkadmin'
go
Following script will create the procedure for changing owner ship.
Just change the SID with ur sid.
2. use SID
go
if object_id('sp_change_sapuser') is not null
drop procedure sp_change_sapuser
go
create procedure sp_change_sapuser @oldid sysname, @newid sysname
as begin
declare @oldid_uid smallint
declare @newid_uid smallint
declare @object sysname
declare @object_full nvarchar(999)
set @oldid_uid = user_id(@oldid)
set @newid_uid = user_id(@newid)
if @oldid_uid is not null and @newid_uid is not null
begin
declare object_cursor cursor local for
select name
from sysobjects
where xtype in ('U', 'V', 'P', 'D')
and name not in ('syssegments','sysconstraints')
and @oldid_uid = uid
open object_cursor
fetch next from object_cursor into @object
while @@fetch_status=0
begin
set @object_full = user_name(@oldid_uid) + '.' + @object
exec sp_changeobjectowner @object_full, @newid
fetch next from object_cursor into @object
end
end
else
if @oldid_uid is null
begin
print '*** old database user does not exist ***'
end
if @newid_uid is null
begin
print '*** new database user does not exist ***'
end
end
executing above created procedure.,
3. exec sp_change_sapuser 'dbo', 'sid'
Language Import How-To
Contents:
Purpose of this document.. 2
Basic documents. 2
Documents in the web. 2
Common OSS notes. 2
Supported Releases. 2
Step-by-step installation of a language.. 3
Preparation phase. 3
Check version of transport tools. 3
Profile maintenance. 3
Maintenance of languages and OS locales. 4
Import phase. 5
Language import 5
Import language of already imported support packages. 6
Language supplementation in client 000. 9
Periodic supplementation in client 000. 10
Copy language to all other clients. 12
Language supplementation in all other clients. 16
Post-treatment of language supplementation. 17
Periodic supplementation in all other clients. 18
Post-Import phase. 20
Activate SAPscript forms. 20
Distribute language templates to ITS servers. 21
Trouble Shooting.. 23
Removing a language. 23
Remove the language supplementation. 23
Remove the language from support packages. 23
Remove the language load. 23
Document created by: Martin Steffke Last change: 13. April 2004
Purpose of this document
This document describes the procedure of how to import a language into an R/3 like system. The complete procedure is reflected in installation guides.
This document does not replace the basic documents from SAP AG.
All information in this document are based on personal exerience and on consulting the developers...
Basic documents
Documents in the web
Please find the basic documents regarding your installed R/3 release in the installation documentation as shown below:
http://intranet.sap.com/instguidesInstallation guides for all SAP products. Follow the document tree on the left:
-> -> -> Language Transport.pdf
http://intranet.sap.com/notesNotes search for OSS notes. Find the language import / transport in component BC-CTS-LAN
Common OSS notes
Please understand the following OSS to support you while trouble shooting the language import:
048047 - Mode of operation of report RSREFILL
432272 - Transport of language data using tp/R3trans
533888 - Example for Language Import and Error Specification
596982 - Texts are deleted by Support Package
Supported Releases
As of now the following releases are supported by this document:
R/3 rel. 4.x to rel. 6.20
ITS rel. 4.6 to rel. 6.20
Step-by-step installation of a language
The following sections contain all the activities of how to install a language
Preparation phase
The preparation phase can be made in advance. During this phase you must restart the R/3 system.
Check version of transport tools
According to the installation guide (Language transport.pdf) you will need to have a minimum version of the transport tools. See also OSS notes:
195442 - Language import and Support Packages
Check this:
SPAM versionTransaction SPAM -> The dialog shows the version
tp versionTransaction STMS -> Button: System Overview -> Mark the current system -> Button: System configuration -> Tab strip: Transport Tool -> Button: Check Transp. Tool -> Open Result Tree: tp-Call -> tp-Version
R3trans versionLog on to the central instance host on operating system level as useradm and enter in a command shell: R3TRANS -> the program displays its version
Profile maintenance
Tell the system about the new languages you are going to install.The parameter zcsa/installed_languages must be set in the DEFAULT profile, not in the instance profile!
Actions:
Login to client 000 as user DDIC oder super-user
RZ10 -> Edit the DEFAULT profile and append the SAP language code (SAP specific) to these parameters: zcsa/installed_languages eu/iwb/installed_languagesIf you don't know SAP language codes: the table T002T contains all SAP language codes:
SE17 -> Table Name = T002T -> Button: Continue -> Fill in the query dialog as shown below:
Press the button: Execute. The result displays all available SAP language codes
Save the DEFAULT profile
Edit the instance profile of all instances and make sure the parameter zcsa/installed_languagesis not contained in any of these profiles.
Save the instance profiles in case you changed them
Restart the R/3 system
Maintenance of languages and OS locales
After restart of the system now introduce the language to the language tool and let the R/3 system check whether all necessary operating system locales are installed.
Did you restart the system after the last check above? (See Profile maintenance). If not, do it now.
Login to client 000 as user DDIC or super user
SE38 -> Start report RSCPINST
In the left part of the screen: Button: Add -> goto the new text line and use the help to find out the ISO language code for the new language:R/3 rel. <= 6.10: R/3 rel. >= 6.20:
Be sure to check the item "Enable locale check":
Press button "Simulate"
If you forgot to restart the R/3 system in advance you will see errors like "Please set profile parameters for the new language". In that case repeat the last chapter Profile maintenance.
If a locale is missing, please let the Operating System group install the locale on all application servers. Example error output for the language "Polish" (PL):
Repeat this step until all errors are resolved.
Press button "Back" to go back to the welcome screen
If the simulation displayed no errors, press button: Activate.
Import phase
Language import
This is the step where you import the language and therefore you need the language CD-ROMs at hand, also the installation guide for questions and concerns. Here is the short How-to:
Login to client 000 as user DDIC or super user
Transaction SMLT -> Button: Classify language (or: New language) ->
Select the new language
Select the supplementation language to be the system language as displayed in the same dialog ath the bottom:
Press the save Button
Mark the language -> Menu: Language -> Import PackageThe language import starts. Please follow the instructions of your language installation guide (see: Documents in the web).
After the language import finishes: Look at the status line of your SAP GUI.If you discover some text in the status line like "Glossary... is not completely installed yet", please run report RSTLAN_AFTER_UPGRADE in the background (SE38 -> Program -> Execute -> Background)
Import language of already imported support packages
If your system has already some support packages applied you have to re-import them - but this time only the language information. See also these OSS notes:
195442 - Language import and Support Packages (common information)
110910 - Deleting the language load (special information concerning report RSLANG20)
Actions:
Login to client 000 as user DDIC or super user
Check which support package were already imported. What R/3 release do you have?
R/3 release <= 6.10SE38 -> Report = "RSTLAN_IMPORT_OCS" -> Import Language = -> Button: Execute
Green traffic light: These support packages are O.K. - no re-import necessary.
Red traffic light: Not O.K. - you need to re-import the support packages
R/3 release >= 6.20SMLT -> Mark the language -> Menu: Language -> Special actions -> Import Support Packages
Green traffic light: These support packages are O.K. - no re-import necessary.
Red traffic light: Not O.K. - you need to re-import the support packages. See below...
Press Button: Go to next screen -> A list of support packages is displayed:
Green traffic light: O.K. These support packages exist in the EPS directory (e.g.: /usr/sap/trans/EPS/in resp. X:\usr\sap\trans\EPS\in)
Red traffic light: Not O.K. You have to download these support packages to the directory DIR_TRANS (e.g.: /usr/sap/trans resp. X:\usr\sap\trans) and to manually unpack them with SAPCAR.
Repeat the following steps as long as there are red traffic lights in the step above:
Download the missing support packages from SAP Service Marketplace and unpack them into DIR_TRANS.(If a package is missing it has the entry "R3trans data file not found" in the column: Status description)
Repeat this step for all downloaded support packages:
Open a new GUI mode (window) with: SE38 -> Report = RSSPDASS -> Press the Button "Yes" only at the first support package, next time press "No":
Enter the name of the support package. You'll find the name in the other GUI mode (window). Press the button: Transport directory
Confirm the upload with "Yes".
Switch back to the GUI mode (window) with the list of support packages and the red traffic lights...
Press button: Back -> Press Button: Go to next screen
Are there still red traffic lights? If yes then repeat all steps from above
Press button: Continue (or: Go to next screen) -> Again check whether all traffic lights are green
If NO: repeat the procedure with the red traffic lights from the last step above
If YES: Press button: Import language data
Dialog: " What should be done with texts of repaired objects" -> Press Button: Overwrite.
Start report RSLANG20 in transaction SE38 -> Fill in the new language, keep all check boxes like this:Start the program as background job: Menu: Program -> Execute in Background -> Select a printer -> select to start the program immediately -> Save the job.
After the Report RSLANG20 finished, enter /$CUA in the OK-code line and press ENTER:
Language supplementation in client 000
Some texts are not yet translated. Anyway the customer needs some text displayed in his GUI. This text is taken from the supplementation language you specified before (see: Language import).
The supplementation job is started first in client 000 since this client is the copy template for languages and forms.
The following OSS notes describe the procedure - sometimes contradictory:
43853 - Language-dependent + client-specific C-tables
211226 - Processing of Customizing in language transport
533888 - Example for Language Import and Error Specification
Actions:
Login to client 000 as user DDIC or super user
SMLT -> Mark the language -> Menu: Language -> Supplement language
In the dialog "Supplement Language" enter a description like: "Supplement with 000". Please enter also the client number as shown...Which R/3 release do you have?
R/3 release <= 6.10Press button: Select -> then button: Execute
R/3 release >= 6.20Check the checkbox: Customizing tables -> button: Execute
You can follow the progress of the supplementation with:SMLT -> Unfold the tree with your language -> Find the button "Job Log" (white paper with glasses) and press it:
Periodic supplementation in client 000
The periodic supplementation is used to supplement language dependent texts after the import of transports, such as Support Packages. The following OSS notes describe the details:
315375 - Periodic language supplementation
533888 - Example for Language Import and Error Specification
Actions:
Login to client 000 as user DDIC or super user
SE38 -> Start report RSTLAN_SUPPLEMENT_PERIODIC and fill in the dialog as follows:
Supplementation template: press in order to select a language from client 000. Example for language NL: Supplement with English , where client=000
Do not press the Button "Execute"!Instead create a periodic batch job in menu: Program -> Execute in background
In dialog "Background Print Parameters":
select a printer, for example LP01.
Set the Spool options: Remove the checkbox item "Print immediately".
See the example below:
In dialog "Start time" plan this job to run periodically every day somewhen in the night (e.g. 23:00 hours). Example:
Save the batch.
Copy language to all other clients
The new language is imported in client 000. Now you should copy the language to all other clients. You have two choices in order to accomplish this:
Client management tools
Advantage: Less post-treatment work at the end. Works better for R/3 application module Logistics..
Disadvantage: More complicated
Language management tools
Advantage: Less complicated
Disadvantage: More post-treatment work due to release-specific implementation.
The following OSS notes concern the copy of languages:
533888 - General procedure
43853 - R/3 release <= 6.10 - Describes the post-treatment measures which OSS note 211226 contains in detail
R/3 release >= 6.20: Transaction SMLT contains all functions mentioned in OSS note 43853
Actions:
Please choose one of the following tools:
Usage of Client management tools
Login to client 000 as user DDIC or super user
SCC4 -> Find out all target clients suitable for the copy process
SCC4 -> Maintain all concerned clients:
The following radiobutton must be cleared: "No changes allowed". If not, clear the flag temporarily. See the dialog with example client 100 below:
SE38 -> Start report RSTLAN_IMPORT_CLIENTS with the following settings:
Field "Import Language Package": Press and select the language from the language import CD. Example below: Language Dutch (NL) for R/3 rel. 4.6C SR2:
Field "Clients": enter all concerned clients. Therefore enter a "000" in the first field and press the button "Multiple selection" to the right. In the following dialog enter all concerned clients from above. Example:
Fill in the remaining fields: "Update mode", "Table class G" and "Display list of tables". Example:
Do not press the Button "Execute"!Instead create a batch job in menu: Program -> Execute in background
In dialog "Background Print Parameters":
select a printer, for example LP01.
Set the Spool options: Remove the checkbox item "Print immediately".
See the example below:
In dialog "Start time" plan this job to start immediately.
Save the batch job
Check the result of batch RSTLAN_IMPORT_CLIENTS in transaction SM37.Therefore look into the spool list, do not look into the batch job protocol.
Now repeat the batch RSTLAN_IMPORT_CLIENTS in SE38.
Use the same settings as above, but this time select the "Language part from support packages". See the example: Language Dutch (NL) for R/3 rel. 4.6C SR2 (sorry, German text below)
Also, start this report as a background job, scheduled for immediate start. See above for detailled screenshots.
Check the result of batch RSTLAN_IMPORT_CLIENTS in transaction SM37.Therefore look into the spool list, do not look into the batch job protocol.
Repeat this step for all concerned clients:
Login to the concerned client as user DDIC or super user
SE38 -> start report RBZMECHK.
Login to client 000 as user DDIC or super user
SCC4 -> Maintain all concerned clients:
If you cleared the radiobutton "No changes allowed" at the beginning above, then re-enable the radiobutton again. See the dialog with example client 100 below:
Usage of Language management tools
Login to client 000 as user DDIC or super user
SCC4 -> Find out all target clients suitable for the copy process
Repeat this step for all concerned clients:
Login to the concerned client as user DDIC or super user
SE38 -> Start report RSTLAN_SUPPLEMENT_UNI, enter the target language code as needed (press the help).
Depending on the R/3 release the dialog looks different. Here is how to continue:
R/3 rel. <= 6.10: Button: Processing of Customizing in language transport -> Button: Execute
R/3 rel. >= 6.20: Button: Client Maintenance with Customizing Translations -> Button: Execute
SE38 -> Start report RBZMECHK.
Language supplementation in all other clients
As you already supplemented the languages in client 000 you now should supplement them in all other clients.
The following OSS notes describe the procedure - sometimes contradictory:
43853 - Language-dependent + client-specific C-tables
211226 - Processing of Customizing in language transport
533888 - Example for Language Import and Error Specification
Actions:
Login to client 000 as user DDIC or super user
SCC4 -> Find out all concerned clients
Repeat this step for all concerned clients:
Login to each concerned client as user DDIC or super user, the logon language must be either DE or EN.
SMLT -> Mark the language -> Menu: Language -> Supplement language
In the dialog "Supplement Language" enter a description like: "Supplement with ". Please enter also the client number as shown...Which R/3 release do you have?
R/3 release <= 6.10Press button: Select -> then button: Execute
R/3 release >= 6.20Check the checkbox: Customizing tables -> button: Execute
You can follow the progress of the supplementation with:SMLT -> Unfold the tree with your language -> Find the button "Job Log" (white paper with glasses) and press it:
Post-treatment of language supplementation
The language supplementation is still implemented with lots of errors. In order to correct the errors proceed as follows:
Actions:
Proceed with this step only if these preconditions are met:
R/3 release is less than 6.10
and you copied the language to other clients using the Usage of Language management tools above.
Error: The tables T006A, T006B and T006C (Units of Measurement) were not translated correctly. The OSS note 451720 shows how to correct this error.
You will need a developer key, an object key and you must create a transport request. Be sure to have all information at hand before starting work.
Create a development class (new name: "package") with the name "SZME". Do this in transaction SE80.
Create an empty report with the name RBZMEREFILL, which belongs to the development class "SZME". Save the report.
Implement the OSS note 451720 using the SAP Notes assistent (transaction SNOTE).
Error: The table T006T (Units of Measurement Texts) was not translated correctly. Translate the Texts manually (!!!) using the original language texts from client 000. You can copy-and-paste the translations... The OSS note 169219 shows this procedure with in another context.
Proceed with this step only if these preconditions are met:
R/3 release is less than or equal to 6.20
and you copied the language to other clients using the Usage of Language management tools above.
Error: The table T006T (Units of Measurement Texts) was not translated correctly. The OSS note 595742 shows how to correct the error.
You will need a developer key, an object key and you must create a transport request. Be sure to have all information at hand before starting work.
Create a development class (new name: "package") with the name "SZME". Do this in transaction SE80.
Create an empty report with the name RBZMETRANS, which belongs to the development class "SZME". Save the report.
Implement the OSS note 595742 using the SAP Notes assistent (transaction SNOTE).
After you started the report RBZMETRANS finally run also the report RBZMECHK
Periodic supplementation in all other clients
The periodic supplementation is used to supplement language dependent texts after the import of transports, such as Support Packages. The following OSS notes describe the details:
315375 - Periodic language supplementation
533888 - Example for Language Import and Error Specification
Actions:
Login to client 000 as user DDIC or super user
SCC4 -> find out all concerned clients
Login to each concerned client as user DDIC or super user, the logon language must be either DE or EN.
SE38 -> Start report RSTLAN_SUPPLEMENT_PERIODIC and fill in the dialog as follows:
Supplementation template: press in order to select a language from the concerned client. Example for language NL: Supplement with English , where client=100
Do not press the Button "Execute"!Instead create a periodic batch job in menu: Program -> Execute in background
In dialog "Background Print Parameters":
select a printer, for example LP01.
Set the Spool options: Remove the checkbox item "Print immediately".
See the example below:
In dialog "Start time" plan this job to run periodically every day somewhen in the night (e.g. after 00:00 hours).Please make sure that only one batch in any client is active at a time!It has been proven to schedule the batch for each client with a minimum gap of 45 minutes in between.Example:
Save the batch.
Post-Import phase
Activate SAPscript forms
SAPscript forms are imported in client 000 only. The following OSS notes describe how to activate the SAPscript forms:
326801 - Activating SAPscript forms after language transport
Actions:
Proceed with this step only if these preconditions are met:
R/3 release is 4.6C (The BASIS release can also be 4.6D)
Login to client 000 as user DDIC or super user
SCC4 -> Find out the clients concerned
Repeat this step for all concerned clients:
Start report RSTXINSH and enter the dialog as follows:
Start report RSTXINSH again and enter the dialog as follows:
Distribute language templates to ITS servers
If your R/3 uses an ITS (Internet Transaction Server) you will need to publish the language templates to all connected ITS. The following OSS notes describe the procedure:
325149 - Publishing IAC objects
412202 - Publishing IAC objects in subsequent import processing
Actions:
Login to client 000 as user DDIC or super user
Start report W3_PUBLISH_SERVICES, do not fill in any dialog fields and just press the button "Execute".
Select the ITS servers where you like to publish the language templates. Therefore proceed like follows:
R/3 rel. <= 6.10
Press button: "Workbench-Settings".
In the following dialog change to the tab strip "Internet Transaction Server"
Select the radio button "On all defined sites" and press the "OK" button (or: "Transfer").Example:
R/3 rel. >= 6.20
Press button: "Workbench-Settings".
In the following dialog change to the tab strip "Internet Transaction Server"
Inside the tab strip select the tab strip "Publish"
Select the radio button "On all defined sites" and press the "OK" button (or: "Transfer").Example:
Back in the main window "Publish Services Chosen" press button "Select all". Now all entries in the list receive a check mark. Example:
Now press the button "Publish" in order to distribute the language templates. Example: See the picture above for the button...
Trouble Shooting
This section is about troubleshooting the language import. May be something went wrong...
Removing a language
If you need to roll-back some actions here is how it works. The roll-back takes place in 3 steps:
Remove language supplementation
Remove language from support packages
Remove the language load
Remove the language supplementation
This is the first step. There exists no OSS note for this procedure.
Actions:
Login to client 000 as user DDIC or super user
SCC4 -> Find out all concerned clients
Repeat this step for all concerned clients. Keep client 000 as the last client for login!
Login to the concerned client as user DDIC or super user
Start the report RSTLAN_SUPPLEMENT_UNI and fill in the dialog as follows:
Field "Target Language": Select the language code of the language to remove
Press button " Reset/Cancel Supplementation of Customizing Tables"
Press button "Execute"
Remove the language from support packages
If you have already supplemented the language, please remove the supplementation first! See Remove the language supplementation above for details.
The following OSS-note describe the procedure:
116756 - Removing language-dep. parts from Support Packages
Actions:
Login to client 000 as user DDIC or super user
Start the report RSTLAN_SUPPLEMENT_UNI and fill in the dialog as follows:
Field "Target Language": Select the language code of the language to remove
Press button " Removing Language Specific Parts from Support Packages"
Press button "Execute"
Remove the language load
If you have already supplemented the language, please remove the supplementation first! See Remove the language supplementation above for details.
If you have already imported support packages, please remove them first! See Remove the language supplementation
This is the first step. There exists no OSS note for this procedure.
Actions:
Login to client 000 as user DDIC or super user
SCC4 -> Find out all concerned clients
Repeat this step for all concerned clients. Keep client 000 as the last client for login!
Login to the concerned client as user DDIC or super user
Start the report RSTLAN_SUPPLEMENT_UNI and fill in the dialog as follows:
Field "Target Language": Select the language code of the language to remove
Press button " Reset/Cancel Supplementation of Customizing Tables"
Press button "Execute"
Remove the language from support packages above for details.
Well, there exists no documented procedure for a language removal.
Keep me updated,
Martin
Contents:
Purpose of this document.. 2
Basic documents. 2
Documents in the web. 2
Common OSS notes. 2
Supported Releases. 2
Step-by-step installation of a language.. 3
Preparation phase. 3
Check version of transport tools. 3
Profile maintenance. 3
Maintenance of languages and OS locales. 4
Import phase. 5
Language import 5
Import language of already imported support packages. 6
Language supplementation in client 000. 9
Periodic supplementation in client 000. 10
Copy language to all other clients. 12
Language supplementation in all other clients. 16
Post-treatment of language supplementation. 17
Periodic supplementation in all other clients. 18
Post-Import phase. 20
Activate SAPscript forms. 20
Distribute language templates to ITS servers. 21
Trouble Shooting.. 23
Removing a language. 23
Remove the language supplementation. 23
Remove the language from support packages. 23
Remove the language load. 23
Document created by: Martin Steffke Last change: 13. April 2004
Purpose of this document
This document describes the procedure of how to import a language into an R/3 like system. The complete procedure is reflected in installation guides.
This document does not replace the basic documents from SAP AG.
All information in this document are based on personal exerience and on consulting the developers...
Basic documents
Documents in the web
Please find the basic documents regarding your installed R/3 release in the installation documentation as shown below:
http://intranet.sap.com/instguidesInstallation guides for all SAP products. Follow the document tree on the left:
->
http://intranet.sap.com/notesNotes search for OSS notes. Find the language import / transport in component BC-CTS-LAN
Common OSS notes
Please understand the following OSS to support you while trouble shooting the language import:
048047 - Mode of operation of report RSREFILL
432272 - Transport of language data using tp/R3trans
533888 - Example for Language Import and Error Specification
596982 - Texts are deleted by Support Package
Supported Releases
As of now the following releases are supported by this document:
R/3 rel. 4.x to rel. 6.20
ITS rel. 4.6 to rel. 6.20
Step-by-step installation of a language
The following sections contain all the activities of how to install a language
Preparation phase
The preparation phase can be made in advance. During this phase you must restart the R/3 system.
Check version of transport tools
According to the installation guide (Language transport.pdf) you will need to have a minimum version of the transport tools. See also OSS notes:
195442 - Language import and Support Packages
Check this:
SPAM versionTransaction SPAM -> The dialog shows the version
tp versionTransaction STMS -> Button: System Overview -> Mark the current system -> Button: System configuration -> Tab strip: Transport Tool -> Button: Check Transp. Tool -> Open Result Tree: tp-Call -> tp-Version
R3trans versionLog on to the central instance host on operating system level as user
Profile maintenance
Tell the system about the new languages you are going to install.The parameter zcsa/installed_languages must be set in the DEFAULT profile, not in the instance profile!
Actions:
Login to client 000 as user DDIC oder super-user
RZ10 -> Edit the DEFAULT profile and append the SAP language code (SAP specific) to these parameters: zcsa/installed_languages eu/iwb/installed_languagesIf you don't know SAP language codes: the table T002T contains all SAP language codes:
SE17 -> Table Name = T002T -> Button: Continue -> Fill in the query dialog as shown below:
Press the button: Execute. The result displays all available SAP language codes
Save the DEFAULT profile
Edit the instance profile of all instances and make sure the parameter zcsa/installed_languagesis not contained in any of these profiles.
Save the instance profiles in case you changed them
Restart the R/3 system
Maintenance of languages and OS locales
After restart of the system now introduce the language to the language tool and let the R/3 system check whether all necessary operating system locales are installed.
Did you restart the system after the last check above? (See Profile maintenance). If not, do it now.
Login to client 000 as user DDIC or super user
SE38 -> Start report RSCPINST
In the left part of the screen: Button: Add -> goto the new text line and use the
Be sure to check the item "Enable locale check":
Press button "Simulate"
If you forgot to restart the R/3 system in advance you will see errors like "Please set profile parameters for the new language". In that case repeat the last chapter Profile maintenance.
If a locale is missing, please let the Operating System group install the locale on all application servers. Example error output for the language "Polish" (PL):
Repeat this step until all errors are resolved.
Press button "Back" to go back to the welcome screen
If the simulation displayed no errors, press button: Activate.
Import phase
Language import
This is the step where you import the language and therefore you need the language CD-ROMs at hand, also the installation guide for questions and concerns. Here is the short How-to:
Login to client 000 as user DDIC or super user
Transaction SMLT -> Button: Classify language (or: New language) ->
Select the new language
Select the supplementation language to be the system language as displayed in the same dialog ath the bottom:
Press the save Button
Mark the language -> Menu: Language -> Import PackageThe language import starts. Please follow the instructions of your language installation guide (see: Documents in the web).
After the language import finishes: Look at the status line of your SAP GUI.If you discover some text in the status line like "Glossary... is not completely installed yet", please run report RSTLAN_AFTER_UPGRADE in the background (SE38 -> Program -> Execute -> Background)
Import language of already imported support packages
If your system has already some support packages applied you have to re-import them - but this time only the language information. See also these OSS notes:
195442 - Language import and Support Packages (common information)
110910 - Deleting the language load (special information concerning report RSLANG20)
Actions:
Login to client 000 as user DDIC or super user
Check which support package were already imported. What R/3 release do you have?
R/3 release <= 6.10SE38 -> Report = "RSTLAN_IMPORT_OCS" -> Import Language =
Green traffic light: These support packages are O.K. - no re-import necessary.
Red traffic light: Not O.K. - you need to re-import the support packages
R/3 release >= 6.20SMLT -> Mark the language -> Menu: Language -> Special actions -> Import Support Packages
Green traffic light: These support packages are O.K. - no re-import necessary.
Red traffic light: Not O.K. - you need to re-import the support packages. See below...
Press Button: Go to next screen -> A list of support packages is displayed:
Green traffic light: O.K. These support packages exist in the EPS directory (e.g.: /usr/sap/trans/EPS/in resp. X:\usr\sap\trans\EPS\in)
Red traffic light: Not O.K. You have to download these support packages to the directory DIR_TRANS (e.g.: /usr/sap/trans resp. X:\usr\sap\trans) and to manually unpack them with SAPCAR.
Repeat the following steps as long as there are red traffic lights in the step above:
Download the missing support packages from SAP Service Marketplace and unpack them into DIR_TRANS.(If a package is missing it has the entry "R3trans data file not found" in the column: Status description)
Repeat this step for all downloaded support packages:
Open a new GUI mode (window) with: SE38 -> Report = RSSPDASS -> Press the Button "Yes" only at the first support package, next time press "No":
Enter the name of the support package. You'll find the name in the other GUI mode (window). Press the button: Transport directory
Confirm the upload with "Yes".
Switch back to the GUI mode (window) with the list of support packages and the red traffic lights...
Press button: Back -> Press Button: Go to next screen
Are there still red traffic lights? If yes then repeat all steps from above
Press button: Continue (or: Go to next screen) -> Again check whether all traffic lights are green
If NO: repeat the procedure with the red traffic lights from the last step above
If YES: Press button: Import language data
Dialog: " What should be done with texts of repaired objects" -> Press Button: Overwrite.
Start report RSLANG20 in transaction SE38 -> Fill in the new language, keep all check boxes like this:Start the program as background job: Menu: Program -> Execute in Background -> Select a printer -> select to start the program immediately -> Save the job.
After the Report RSLANG20 finished, enter /$CUA in the OK-code line and press ENTER:
Language supplementation in client 000
Some texts are not yet translated. Anyway the customer needs some text displayed in his GUI. This text is taken from the supplementation language you specified before (see: Language import).
The supplementation job is started first in client 000 since this client is the copy template for languages and forms.
The following OSS notes describe the procedure - sometimes contradictory:
43853 - Language-dependent + client-specific C-tables
211226 - Processing of Customizing in language transport
533888 - Example for Language Import and Error Specification
Actions:
Login to client 000 as user DDIC or super user
SMLT -> Mark the language -> Menu: Language -> Supplement language
In the dialog "Supplement Language" enter a description like: "Supplement with
R/3 release <= 6.10Press button: Select -> then button: Execute
R/3 release >= 6.20Check the checkbox: Customizing tables -> button: Execute
You can follow the progress of the supplementation with:SMLT -> Unfold the tree with your language -> Find the button "Job Log" (white paper with glasses) and press it:
Periodic supplementation in client 000
The periodic supplementation is used to supplement language dependent texts after the import of transports, such as Support Packages. The following OSS notes describe the details:
315375 - Periodic language supplementation
533888 - Example for Language Import and Error Specification
Actions:
Login to client 000 as user DDIC or super user
SE38 -> Start report RSTLAN_SUPPLEMENT_PERIODIC and fill in the dialog as follows:
Supplementation template: press
Do not press the Button "Execute"!Instead create a periodic batch job in menu: Program -> Execute in background
In dialog "Background Print Parameters":
select a printer, for example LP01.
Set the Spool options: Remove the checkbox item "Print immediately".
See the example below:
In dialog "Start time" plan this job to run periodically every day somewhen in the night (e.g. 23:00 hours). Example:
Save the batch.
Copy language to all other clients
The new language is imported in client 000. Now you should copy the language to all other clients. You have two choices in order to accomplish this:
Client management tools
Advantage: Less post-treatment work at the end. Works better for R/3 application module Logistics..
Disadvantage: More complicated
Language management tools
Advantage: Less complicated
Disadvantage: More post-treatment work due to release-specific implementation.
The following OSS notes concern the copy of languages:
533888 - General procedure
43853 - R/3 release <= 6.10 - Describes the post-treatment measures which OSS note 211226 contains in detail
R/3 release >= 6.20: Transaction SMLT contains all functions mentioned in OSS note 43853
Actions:
Please choose one of the following tools:
Usage of Client management tools
Login to client 000 as user DDIC or super user
SCC4 -> Find out all target clients suitable for the copy process
SCC4 -> Maintain all concerned clients:
The following radiobutton must be cleared: "No changes allowed". If not, clear the flag temporarily. See the dialog with example client 100 below:
SE38 -> Start report RSTLAN_IMPORT_CLIENTS with the following settings:
Field "Import Language Package": Press
Field "Clients": enter all concerned clients. Therefore enter a "000" in the first field and press the button "Multiple selection" to the right. In the following dialog enter all concerned clients from above. Example:
Fill in the remaining fields: "Update mode", "Table class G" and "Display list of tables". Example:
Do not press the Button "Execute"!Instead create a batch job in menu: Program -> Execute in background
In dialog "Background Print Parameters":
select a printer, for example LP01.
Set the Spool options: Remove the checkbox item "Print immediately".
See the example below:
In dialog "Start time" plan this job to start immediately.
Save the batch job
Check the result of batch RSTLAN_IMPORT_CLIENTS in transaction SM37.Therefore look into the spool list, do not look into the batch job protocol.
Now repeat the batch RSTLAN_IMPORT_CLIENTS in SE38.
Use the same settings as above, but this time select the "Language part from support packages". See the example: Language Dutch (NL) for R/3 rel. 4.6C SR2 (sorry, German text below)
Also, start this report as a background job, scheduled for immediate start. See above for detailled screenshots.
Check the result of batch RSTLAN_IMPORT_CLIENTS in transaction SM37.Therefore look into the spool list, do not look into the batch job protocol.
Repeat this step for all concerned clients:
Login to the concerned client as user DDIC or super user
SE38 -> start report RBZMECHK.
Login to client 000 as user DDIC or super user
SCC4 -> Maintain all concerned clients:
If you cleared the radiobutton "No changes allowed" at the beginning above, then re-enable the radiobutton again. See the dialog with example client 100 below:
Usage of Language management tools
Login to client 000 as user DDIC or super user
SCC4 -> Find out all target clients suitable for the copy process
Repeat this step for all concerned clients:
Login to the concerned client as user DDIC or super user
SE38 -> Start report RSTLAN_SUPPLEMENT_UNI, enter the target language code as needed (press the
Depending on the R/3 release the dialog looks different. Here is how to continue:
R/3 rel. <= 6.10: Button: Processing of Customizing in language transport -> Button: Execute
R/3 rel. >= 6.20: Button: Client Maintenance with Customizing Translations -> Button: Execute
SE38 -> Start report RBZMECHK.
Language supplementation in all other clients
As you already supplemented the languages in client 000 you now should supplement them in all other clients.
The following OSS notes describe the procedure - sometimes contradictory:
43853 - Language-dependent + client-specific C-tables
211226 - Processing of Customizing in language transport
533888 - Example for Language Import and Error Specification
Actions:
Login to client 000 as user DDIC or super user
SCC4 -> Find out all concerned clients
Repeat this step for all concerned clients:
Login to each concerned client as user DDIC or super user, the logon language must be either DE or EN.
SMLT -> Mark the language -> Menu: Language -> Supplement language
In the dialog "Supplement Language" enter a description like: "Supplement with
R/3 release <= 6.10Press button: Select -> then button: Execute
R/3 release >= 6.20Check the checkbox: Customizing tables -> button: Execute
You can follow the progress of the supplementation with:SMLT -> Unfold the tree with your language -> Find the button "Job Log" (white paper with glasses) and press it:
Post-treatment of language supplementation
The language supplementation is still implemented with lots of errors. In order to correct the errors proceed as follows:
Actions:
Proceed with this step only if these preconditions are met:
R/3 release is less than 6.10
and you copied the language to other clients using the Usage of Language management tools above.
Error: The tables T006A, T006B and T006C (Units of Measurement) were not translated correctly. The OSS note 451720 shows how to correct this error.
You will need a developer key, an object key and you must create a transport request. Be sure to have all information at hand before starting work.
Create a development class (new name: "package") with the name "SZME". Do this in transaction SE80.
Create an empty report with the name RBZMEREFILL, which belongs to the development class "SZME". Save the report.
Implement the OSS note 451720 using the SAP Notes assistent (transaction SNOTE).
Error: The table T006T (Units of Measurement Texts) was not translated correctly. Translate the Texts manually (!!!) using the original language texts from client 000. You can copy-and-paste the translations... The OSS note 169219 shows this procedure with in another context.
Proceed with this step only if these preconditions are met:
R/3 release is less than or equal to 6.20
and you copied the language to other clients using the Usage of Language management tools above.
Error: The table T006T (Units of Measurement Texts) was not translated correctly. The OSS note 595742 shows how to correct the error.
You will need a developer key, an object key and you must create a transport request. Be sure to have all information at hand before starting work.
Create a development class (new name: "package") with the name "SZME". Do this in transaction SE80.
Create an empty report with the name RBZMETRANS, which belongs to the development class "SZME". Save the report.
Implement the OSS note 595742 using the SAP Notes assistent (transaction SNOTE).
After you started the report RBZMETRANS finally run also the report RBZMECHK
Periodic supplementation in all other clients
The periodic supplementation is used to supplement language dependent texts after the import of transports, such as Support Packages. The following OSS notes describe the details:
315375 - Periodic language supplementation
533888 - Example for Language Import and Error Specification
Actions:
Login to client 000 as user DDIC or super user
SCC4 -> find out all concerned clients
Login to each concerned client as user DDIC or super user, the logon language must be either DE or EN.
SE38 -> Start report RSTLAN_SUPPLEMENT_PERIODIC and fill in the dialog as follows:
Supplementation template: press
Do not press the Button "Execute"!Instead create a periodic batch job in menu: Program -> Execute in background
In dialog "Background Print Parameters":
select a printer, for example LP01.
Set the Spool options: Remove the checkbox item "Print immediately".
See the example below:
In dialog "Start time" plan this job to run periodically every day somewhen in the night (e.g. after 00:00 hours).Please make sure that only one batch in any client is active at a time!It has been proven to schedule the batch for each client with a minimum gap of 45 minutes in between.Example:
Save the batch.
Post-Import phase
Activate SAPscript forms
SAPscript forms are imported in client 000 only. The following OSS notes describe how to activate the SAPscript forms:
326801 - Activating SAPscript forms after language transport
Actions:
Proceed with this step only if these preconditions are met:
R/3 release is 4.6C (The BASIS release can also be 4.6D)
Login to client 000 as user DDIC or super user
SCC4 -> Find out the clients concerned
Repeat this step for all concerned clients:
Start report RSTXINSH and enter the dialog as follows:
Start report RSTXINSH again and enter the dialog as follows:
Distribute language templates to ITS servers
If your R/3 uses an ITS (Internet Transaction Server) you will need to publish the language templates to all connected ITS. The following OSS notes describe the procedure:
325149 - Publishing IAC objects
412202 - Publishing IAC objects in subsequent import processing
Actions:
Login to client 000 as user DDIC or super user
Start report W3_PUBLISH_SERVICES, do not fill in any dialog fields and just press the button "Execute".
Select the ITS servers where you like to publish the language templates. Therefore proceed like follows:
R/3 rel. <= 6.10
Press button: "Workbench-Settings".
In the following dialog change to the tab strip "Internet Transaction Server"
Select the radio button "On all defined sites" and press the "OK" button (or: "Transfer").Example:
R/3 rel. >= 6.20
Press button: "Workbench-Settings".
In the following dialog change to the tab strip "Internet Transaction Server"
Inside the tab strip select the tab strip "Publish"
Select the radio button "On all defined sites" and press the "OK" button (or: "Transfer").Example:
Back in the main window "Publish Services Chosen" press button "Select all". Now all entries in the list receive a check mark. Example:
Now press the button "Publish" in order to distribute the language templates. Example: See the picture above for the button...
Trouble Shooting
This section is about troubleshooting the language import. May be something went wrong...
Removing a language
If you need to roll-back some actions here is how it works. The roll-back takes place in 3 steps:
Remove language supplementation
Remove language from support packages
Remove the language load
Remove the language supplementation
This is the first step. There exists no OSS note for this procedure.
Actions:
Login to client 000 as user DDIC or super user
SCC4 -> Find out all concerned clients
Repeat this step for all concerned clients. Keep client 000 as the last client for login!
Login to the concerned client as user DDIC or super user
Start the report RSTLAN_SUPPLEMENT_UNI and fill in the dialog as follows:
Field "Target Language": Select the language code of the language to remove
Press button " Reset/Cancel Supplementation of Customizing Tables"
Press button "Execute"
Remove the language from support packages
If you have already supplemented the language, please remove the supplementation first! See Remove the language supplementation above for details.
The following OSS-note describe the procedure:
116756 - Removing language-dep. parts from Support Packages
Actions:
Login to client 000 as user DDIC or super user
Start the report RSTLAN_SUPPLEMENT_UNI and fill in the dialog as follows:
Field "Target Language": Select the language code of the language to remove
Press button " Removing Language Specific Parts from Support Packages"
Press button "Execute"
Remove the language load
If you have already supplemented the language, please remove the supplementation first! See Remove the language supplementation above for details.
If you have already imported support packages, please remove them first! See Remove the language supplementation
This is the first step. There exists no OSS note for this procedure.
Actions:
Login to client 000 as user DDIC or super user
SCC4 -> Find out all concerned clients
Repeat this step for all concerned clients. Keep client 000 as the last client for login!
Login to the concerned client as user DDIC or super user
Start the report RSTLAN_SUPPLEMENT_UNI and fill in the dialog as follows:
Field "Target Language": Select the language code of the language to remove
Press button " Reset/Cancel Supplementation of Customizing Tables"
Press button "Execute"
Remove the language from support packages above for details.
Well, there exists no documented procedure for a language removal.
Keep me updated,
Martin
Subscribe to:
Posts (Atom)
