Beruflich Dokumente
Kultur Dokumente
&RQWHQWV
Overview ................................................................................................................22–2
Retrieving Files from SAP, SAPSERV4 ..............................................................22–2
EarlyWatch Session............................................................................................22–14
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.
:K\
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
81,;
+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).
3UHUHTXLVLWHV
$Q([DPSOHRIDQ)73&OLHQW
*XLGHG7RXU
Release 4.6A/B
22–4
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.
Release 4.6A/B
22–6
Chapter 22: Remote Services
Retrieving Files from SAP, SAPSERV4
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.
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
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
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.
6SHFLDO6$31HW1RWHV
Note # Function
(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
:K\
: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.
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.
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.
Release 4.6A/B
22–16