Sie sind auf Seite 1von 16

&KDSWHU 5HPRWH6HUYLFHV

&RQWHQWV

Overview ................................................................................................................22–2
Retrieving Files from SAP, SAPSERV4 ..............................................................22–2
EarlyWatch Session............................................................................................22–14

System Administration Made Easy 22–1


Chapter 22: Remote Services
Overview

2YHUYLHZ

In this chapter, readers will learn about SAPSERV4 and EarlyWatch. The information in this
chapter should help the user understand how to:
< Retrieve files from SAP and SAPSERV4
< Connect to SAPSERV4
< Download files
< Arrange for an EarlyWatch session

5HWULHYLQJ)LOHVIURP6$36$36(59

:KDW

SAPSERV is a series of servers that contain patches and other downloadable files for
customers. In this guidebook, we specifically discuss the U.S. server, SAPSERV4. The
difference between the various SAPSERV servers is the name, the IP address, and the
location (see table below). At present, we are not aware of any plans to move this
functionality to SAPNet–Web.

Location Host IP Address Long Hostname

Walldorf sapserv3 147.204.2.5 sapserv3.wdf.sap-ag.de


Foster City sapserv4 204.79.199.2 sapserv4.sfo.sap-ag.de
Tokyo sapserv5 194.39.138.2 sapserv5.tyo.sap-ag.de
Sydney sapserv6 194.39.139.16 sapserv6.syd.sap-ag.de
Singapore sapserv7 194.39.134.35 sapserv7.sin.sap-ag.de

:K\

The following types of files are retrieved from SAPSERV4:


< Updates to the R/3 System kernel.
< Various patches, such as:
ΠR/3 System
ΠDatabase
ΠSAP GUI
< Miscellaneous downloadable files.

Release 4.6A/B
22–2
Chapter 22: Remote Services
Retrieving Files from SAP, SAPSERV4

:KHUH

If you cannot connect to SAPSERV4, you may not be on the machine where SAProuter is
installed.
The SAProuters at SAP are configured to only recognize their counterpart SAProuter on the
customer’s side. Therefore, you must connect from the computer where the SAProuter is
installed and running.

17

You must either:


< Be physically on the NT server where the SAProuter is installed.
< Use a remote control program to take over the server where the SAProuter is installed.

81,;

You must either:


< Be physically on the UNIX server where the SAProuter is installed
< Telnet to the server where the SAProuter is installed.

+RZ

You can connect to, navigate within, and download files from SAPSERV4 using:
< Command prompt
< Windows FTP GUI client
< Internet browser

For ease of use and navigation, use an FTP GUI client to access SAPSERV.

&RQQHFWLQJWR6$36(598VLQJD*8, 17 
Using an FTP GUI client is much easier than using the command prompt.

In this guidebook, we use only one of the many available FTP clients. Other FTP clients are
listed in the resources section of appendix A. SAP does not endorse any particular product.
Also, it is your responsibility to perform compatibility testing to determine if the software
you select functions on your system without conflict (for example, without crashing the
system).

System Administration Made Easy


22–3
Chapter 22: Remote Services
Retrieving Files from SAP, SAPSERV4

3UHUHTXLVLWHV

Before attempting a connection to SAPSERV4 using a GUI, make certain that:


< The SAP service connection to SAPSERV4 has been established, tested, and is functional.
< An FTP client is installed on the computer where the SAProuter is located.
< The FTP client has been configured with the following parameters:
ΠIP address of SAPSERV4, 204.79.199.2
ΠLogin user ID, FTP
ΠUser password <your e-mail address>
ΠDirectory to download files to on the client PC (optional)

$Q([DPSOHRIDQ)73&OLHQW

*XLGHG7RXU


The following example of an FTP client is courtesy of Van Dyke Technologies.


1. Start the FTP client program.
2. Connect to SAPSERV4.

Release 4.6A/B
22–4
Chapter 22: Remote Services
Retrieving Files from SAP, SAPSERV4

3. Navigate down the tree structure


to the directory that contains the
file(s) you need.

4. In some directories, there are


informational files ( .message and
*.info) that you should download
and read. 4
5. Select the file(s) you want to
download.
*.CAR (program) files must be 5
downloaded in binary format.

System Administration Made Easy


22–5
Chapter 22: Remote Services
Retrieving Files from SAP, SAPSERV4

&RQQHFWLQJWR6$36(598VLQJWKH&RPPDQG3URPSW
1DYLJDWLQJLQ6$36(59
SAPSERV4 is a UNIX server.
< UNIX differences to remember for NT users:
ΠUNIX is a case-sensitive operating system, NT is not. When navigating in SAPSERV4
or downloading a file, enter the directory or filename exactly as it is displayed (for
example, Rel40B is not the same as rel40b).
ΠUNIX commands differ from NT commands (for example, dir [NT] = ls [UNIX] ).
< Important UNIX commands:
Πls List (similar to the dir command in NT and DOS)
Πcd Change directory (similar to the cd command in NT and DOS)
Πget Get or download a file
Πbin Switch to binary mode, to download programs
Πbye Log off

&RQQHFWLQJDWWKH&RPPDQG3URPSW

*XLGHG7RXU


Both UNIX and NT use a command prompt window, and the commands entered are the same. The NT
command prompt window is shown in the following example.

The directory you are currently in is the directory into which file will be downloaded. To
download the file to a different directory, change to that directory after you open the
command prompt window and before you enter the FTP command.

1. Open a Command Prompt window.


2. As an option, you can change to 2
your download directory.
3. Enter ftp 204.79.199.2
If your network personnel put
sapserv4 into the hosts file or DNS,
you can enter ftp sapverv4
after the prompt.
In this example, the file(s) will
download to the root directory of
the C drive.

Release 4.6A/B
22–6
Chapter 22: Remote Services
Retrieving Files from SAP, SAPSERV4

4. Enter ftp at the User prompt.


5. Enter your e-mail address at the
Password: prompt. 4
5

6. From this screen, use the cd


command to navigate through the
directory structure.
A portion of the SAPSERV4
directory structure is provided at
the end of this chapter to help you
navigate within SAPSERV.

In NT, to increase the screen buffer size and prevent the text from scrolling off the screen:
1. On the NT desktop, choose My Computer → Control Panel → Console→ Layout tab.
2. Under screen buffer size, increase the height to 100.

System Administration Made Easy


22–7
Chapter 22: Remote Services
Retrieving Files from SAP, SAPSERV4

7. The navigation commands are cd


and ls.
7
This is the directory for Release
4.0b HPUX Oracle
8. There are informational files
8
(.message and *.info) that we
recommend you download and
read.
9. Remember the file you want to
download, because you will enter
the filename later.
The files indicated are only for
example.

Release 4.6A/B
22–8
Chapter 22: Remote Services
Retrieving Files from SAP, SAPSERV4

'RZQORDGLQJ)LOHV
< Download patches, kernels, transports, and other files in binary format.
< Many of the files are in *.CAR archives.
Use the CAR program to unpack these files (see Unpacking a CAR file on page 22–13).

*XLGHG7RXU


For text files ( .message and *.info), skip


to step 2.
1. For binary files, such as patches,
kernels, and transports (with the
1
.CAR extension), to switch to
2
binary mode, enter bin at the ftp
prompt.
4
2. Enter get <filename> to
download the file (for example,
get sapdba_60.CAR).
Filenames are case sensitive.
3. Press Enter.
4. Wait for the download to finish
and the ftp prompt to appear.
This screen shows an example of
an information file, in this case
dw.info (a text file that contains the
patch level of the kernel).

System Administration Made Easy


22–9
Chapter 22: Remote Services
Retrieving Files from SAP, SAPSERV4

Scroll down to view a listing (by patch


level) of what is fixed in the kernel
patch.

3DUWLDO2UJDQL]DWLRQRI6$36(59
Not all directories on SAPSERV4 are listed or expanded. For those that are similar (release, database,
operating system), only one is expanded in detail. Over time, the directory structure may change or be
reorganized. See below for the SAPSERV4 structure.

Release 4.6A/B
22–10
Chapter 22: Remote Services
Retrieving Files from SAP, SAPSERV4

general ----------------------------------------------------------for all corrections that generally apply to customers


3rdparty --------------------------------------------database and hardware specific
adabas
compaq
datageneral
db2
informix
mssql
oracle
sni (Seimens)
frontend
patches ----------------------------------patches to the SAPGUI
rel31H
rel31I
rel40A
rel40B
windows
win16
win32
rel45A
sapgui -----------------------------------released SAPGUI
apple
nt
30f
30f_r2
31G
31H
40A
pre_release
os2
win
saplpd (spool)
barcode
NT
WIN
LPRINT
alphaosf
hp
NT
rm600
rs6000
sun
WIN
NT
rel30F
rel31G
rel31H
rel40A
rel40B
rel45A
rel45B
WIN
R3server
A abap
note.*-------------------------corrections specific to a note number
binaries

System Administration Made Easy


22–11
Chapter 22: Remote Services
Retrieving Files from SAP, SAPSERV4

R3server
abap
note.* corrections specific to a note number
binaries
NT
support
i386
UNIX
languages
Note.*-------------------------specific note numbers
patches -----------------------------------R/3 patches, where most of the downloads will be
COMMON ------------------Kernel, release-independent programs
NT
i386 ---this dir has car.exe, sappad.exe, tar.exe
OS400
UNIX
NT
ALPHA
I386 ---------------this dir has car.exe, sappad.exe, tar.exe
MSSQL
rel31H
rel31I
rel40A
rel40B -----------------------Kernel release, OS, hardware, db specific programs
NT
I386
MSS --------------MS SQLserver
ORA --------------Oracle
OS400
UNIX
AIX
DEC
HPUX
ORA
HPUX_SHM
RELIANT
SOLARIS
rel45A

Release 4.6A/B
22–12
Chapter 22: Remote Services
Retrieving Files from SAP, SAPSERV4

8QSDFNLQJD&$5)LOH

:KDW

A CAR file is a packaged file similar to a zip file. Like a zip file, a CAR file may contain
more than one file. SAP delivers transports, patches, and other programs and files in CAR
files. To use the contents of these files, you must unpack them using car.exe.

3UHUHTXLVLWHV

1. Get car.exe from SAPSERV4 (for the latest version) or from the directory
NT: \usr\sap\<sid>\sys\exe\run\
UNIX: /usr/sap/<sid>/SYS/exe/run

If your version of the CAR program is older than six months, replace it with the latest
version.

2. Create an “unpacking” directory where you “unpack” files (for example, d:\sap\unpack).
3. Copy the file car.exe into this directory.

8QSDFNLQJD)LOH

*XLGHG7RXU


To reduce confusion:
< Begin the “unpacking” session with only the car.exe program in the unpacking
directory.
< Handle only one CAR file at a time.
Complete everything for that file before proceeding to the next file.

1. Copy the file to be unpacked into the unpacking directory (for example, sapdba_64.car).
2. Open a command prompt window.
3. Change to the unpacking directory.

System Administration Made Easy


22–13
Chapter 22: Remote Services
EarlyWatch Session

4. Execute the unpack command,


car –xvf <file-name>
(for example,
car –xvf sapdba_64.CAR).
The file will be unpacked into the
unpacking directory.
5. Move the unpacked files to where
you need them. 4
6. Clean the unpacking directory by
deleting all files, except the car.exe
file.

6SHFLDO6$31HW1RWHV

Note # Function

29372 Unpacking CAR archives


63786 FAQ – Frequently Asked Questions: sapservX
63845 Corrections on SAPSERV4 – searching for files
96885 Downloading a front-end patch from SAPSERVx

(DUO\:DWFK6HVVLRQ

:KDW

The underlying concept of EarlyWatch is to prevent problems before they occur or escalate.
EarlyWatch diagnoses a system’s potential problems and resource bottlenecks so they can
be resolved in advance.
During an EarlyWatch session, performance experts log on to your system (into client 066)
to monitor its performance, review its performance-related configuration settings, and
recommend changes to your system.
Analysis is done in five areas:
< R/3 configuration
< R/3 application
< Server
< Workload
< Database
EarlyWatch applies only to the production system, not the development system. The goal is
for satisfactory online performance, not background performance. A system, other than the

Release 4.6A/B
22–14
Chapter 22: Remote Services
EarlyWatch Session

production, is difficult to tune to a moderate degree and is almost impossible to tune


optimally. This difficulty is because the activity in a development or test environment is not
regular or consistent; development activity can vary greatly from week to week.

:K\

EarlyWatch’s primary function is to improve the online performance of the production


system.

:KHQ
< A couple of months after going live
< After implementing significant changes to your system, such as:
ΠNew modules
ΠExpansion of existing modules
ΠAddition of significant numbers of users to the system
These and similar items change the workload to the system. This change could render
the existing EarlyWatch parameters inapplicable. As your system or company
conditions change, we recommend that you request a new EarlyWatch session.

You do not have to do an EarlyWatch session if your system or company conditions have
remained the same.

< After experiencing significant degradation of online performance


This condition should be a steady condition and not an intermittent spike.

 1RWH The target response is “less than 1 second,” which excludes the network delay
from the user’s PC to the R/3 System. This delay is outside the scope and control of SAP.

+RZ
1. The customer contacts SAP to arrange for an EarlyWatch session at:
SAP America, Inc. EarlyWatch
600 East Las Colinas Blvd, Ste. 2000
Irving, TX 75039
Tel.: (800) 677-7271 or (972) 868-2094
FAX: (972) 868-2108
2. There are prerequisites to an EarlyWatch session and you will be advised of them.
These prerequisites may require technical assistance to apply.
3. The customer opens the SAP service connection to the production system for
EarlyWatch.
4. EarlyWatch connects to client 066 on the production system via SAP service connection
to gather data and record configuration. Client 066 is reserved exclusively for
EarlyWatch.

System Administration Made Easy


22–15
Chapter 22: Remote Services
EarlyWatch Session

5. Once the customer’s system is analyzed, a report is generated and sent to the customer.
Recommendations may be at any of three levels:
< R/3 System
< Database
< Operating system
6. The customer reviews the report and recommendations.

If you have any questions about the report, discuss them with the EarlyWatch analyst.
If a recommended change seems drastic or does not make sense, discuss it with the
analyst before proceeding. Mistakes have been made.
Try to understand the recommendations made by EarlyWatch. As a system
administrator, the R/3 System is your responsibility.

7. After the review, apply the recommendations to your system.


8. Monitor your system for signs of problems.

Release 4.6A/B
22–16