2. SAP AG 2003, Title of Presentation, Speaker Name / 2
Objectives of the Test
Prove that the SAP GUI release 4.6D remains an ultra-thin client
Compare network load of SAP GUI for Windows 32-bit and SAP
GUI on WTS with Citrix Meta Frame
3. SAP AG 2003, Title of Presentation, Speaker Name / 3
Test Environment
Front-end
Windows Terminal Server SAP R/3 Server
Measure Point
SAP Network
Ethernet 10 Mbit/sec
4. SAP AG 2003, Title of Presentation, Speaker Name / 4
Hardware and Software of Used For the Test
Frontend
Notebook PIII 500 MHz
128 MB Memory
10 GB Hard disk
Windows Terminal Server
4 Processor 550 MHz
2 GB Memory
2x9 GB Hard disk Raid1
Raid Controller 64 MB
R/3 Server
4.6C Benchmark system
Frontend
MS Windows 2000
SAPGUI 4.6 D (8849)
Citrix ICA-Client 1.8, 6.00.931
Windows Terminal Server
MS Windows NT 4.0 Terminal
Server
Citrix Metaframe 1.8
R/3 Server
4.6 C Support Pack 13
Hardware Software
5. SAP AG 2003, Title of Presentation, Speaker Name / 5
Business Process Tested: SD
The following transaction was run through
Create Order
Also part of the Sales & Distribution (SD) Standard Application
Benchmark
Individual steps
1st Step -> Create Order / nVA01
2nd Step -> Enter Header Data
3rd Step -> Enter five items
4th Step -> Save Order
6. SAP AG 2003, Title of Presentation, Speaker Name / 6
Configuration Software
Local SAP GUI
1st Test using a local configuration
2nd Test using Low Speed Connection (LSC)
ICA-Client
1st Test -> LAN configuration
User data compression
2nd Test -> WAN configuration
User data compression
User disk cache for bitmaps
Queue mouse movements and keystroke
SpeedScreen -> On -> Mouse Click and Local Text Echo
The tests are repeated once to see effects with caching
7. SAP AG 2003, Title of Presentation, Speaker Name / 7
Result: Total Number of Received Bytes
78.700
50.500
42.500
22.600
27.412
14.527
0
10,000
20,000
30,000
40,000
50,000
60,000
70,000
80,000
90,000
LAN connection
SAP GUI WTS 1st run
SAP GUI WTS 2nd run
(cache)
Local SAP GUI, both runs
WAN connection
8. SAP AG 2003, Title of Presentation, Speaker Name / 8
SAPGUI LAN
(no LSC)
SAPGUI WAN
with LSC
WTS LAN
data compress
WTS WAN
all flags
Bytes delta Bytes delta Bytes delta Bytes delta
First run
Start 0 0 0 0
1st Step 4.039 4.039 1.015 1.015 9.700 9.700 6.700 6.700
2nd Step 15.069 11.030 6.307 5.292 28.300 18.600 23.100 16.400
3rd Step 21.605 6.536 10.730 4.423 57.100 28.800 43.500 20.400
4th Step 27.412 5.807 14.527 3.797 78.700 21.600 50.500 7.000
27.412 14.527 78.700 50.500
Second run
Start 0 0 0 0
1st Step 4.039 4.039 1.015 1.015 4.500 4.500 1.200 1.200
2nd Step 15.069 11.030 6.307 5.292 10.112 5.612 4.300 3.100
3rd Step 21.605 6.536 10.730 4.423 31.656 21.544 18.900 14.600
4th Step 27.412 5.807 14.527 3.797 42.500 10.844 22.600 3.700
27.412 14.527 42.500 22.600
Result: Network Load Details
Enter 5 items
9. SAP AG 2003, Title of Presentation, Speaker Name / 9
Business Process Tested: BW Workbench
The following transaction was run through
Start BEX-Analyzer
Open Workbech
Also part of the Business Warehouse (BW) Standard Application
Benchmark
Individual steps
1st Step -> Start BEX-Analyzer, Open Workbench without scrolling
2nd Step -> Close Excel
The tests are repeated once to see effects with caching
10. SAP AG 2003, Title of Presentation, Speaker Name / 10
Result: Total Number of Received Bytes BW
Workbench
LAN connection
SAP GUI WTS
1st run
SAP GUI WTS
2nd run (cache)
Local SAP GUI,
both runs
WAN connection
Start BEX-Analyzer, Open Workbook, Close Workbook
261,636 262,090
36,067 38,100
18,800 12,400
0
50,000
100,000
150,000
200,000
250,000
300,000
11. SAP AG 2003, Title of Presentation, Speaker Name / 11
SAPGUI LAN
(no LSC)
WTS LAN
data compress
WTS WAN
all flags
Bytes delta Bytes delta Bytes delta
First run
Start 0 0 0
1st Step 254.280 254.280 30.081 30.081 32.700 32.700
2nd Step 261.636 7.356 36.067 5.986 38.100 5.400
261.636 36.067 38.100
Second run
Start 0 0 0
1st Step 254.880 14.640 9.500 9.500
2nd Step 262.090 7.210 18.800 4.160 12.400 2.900
262.090 18.800 12.400
Result: Network Load Details BW Workbench
254.880 14.640
Start BEX-Analyzer, Open Workbook, Close Workbook
12. SAP AG 2003, Title of Presentation, Speaker Name / 12
Business Process Tested BW Workbench
The following transaction was run through
Start BEX-Analyzer
Open Workbech
Also part of the Business Warehouse (BW) Standard Application
Benchmark
Individual steps
1st Step -> Start BEX-Analyzer, Open Workbench without scrolling
2nd Step -> Refresh in BEX-Analyzer
The tests are repeated once to see effects with caching
13. SAP AG 2003, Title of Presentation, Speaker Name / 13
Result: Total Number of Received Bytes BW
Workbench
LAN connection WAN connection
Start BEX-Analyzer, Open Workbook, Refresh Workbook
SAP GUI WTS
1st run
SAP GUI WTS
2nd run (cache)
Local SAP GUI,
both runs
310,608 318,100
57,990 51,700
31,500
18,500
0
50,000
100,000
150,000
200,000
250,000
300,000
350,000
14. SAP AG 2003, Title of Presentation, Speaker Name / 14
SAPGUI LAN
(no LSC)
WTS LAN
data compress
WTS WAN
all flags
Bytes delta Bytes delta Bytes delta
First run
Start 0 0 0
1st Step 253.800 253.800 36.600 36.600 33.178 31.178
2nd Step 310.608 56.808 57.990 21.390 51.700 18.522
310.608 57.990 51.700
Second run
Start 0 0 0
1st Step 261.548 17.600 9.024 9.024
2nd Step 318.100 56.552 31.500 13.900 18.500 9.476
318.100 31.500 18.500
Result: Network Load Details BW Workbench
261.548 17.600
Start BEX-Analyzer, Open Workbook, Refresh Workbook
15. SAP AG 2003, Title of Presentation, Speaker Name / 15
Business Process Tested: APO – Demand Planning
The following transaction was run through
Logon
Transaction: DP/SNP Interactive Demand Planning
Also part of the Advanced Planner and Optimizer (APO) Standard
Application Benchmark
Individual steps
1st Step -> Logon
2nd Step -> Start Transaction: DP/SNP Interactive Demand Planning
3nd Step -> Load selection profile
4nd Step -> Do selection / load data
5nd Step -> Calculate statistics and go back
The tests are repeated once to see effects with caching
16. SAP AG 2003, Title of Presentation, Speaker Name / 16
Result: Total Number of Received Bytes APO
LAN connection WAN connection
Logon, Start transaction, Load profile, Do selection/load data, Calculate
SAP GUI WTS
1st run
SAP GUI WTS
2nd run (cache)
Local SAP GUI,
both runs
165,800
143,636
320,112
312,051
32,872 23,466
0
50,000
100,000
150,000
200,000
250,000
300,000
350,000
17. SAP AG 2003, Title of Presentation, Speaker Name / 17
SAPGUI LAN
(no LSC)
SAPGUI WAN
with LSC
WTS LAN
data compress
WTS WAN
all flags
Bytes delta Bytes delta Bytes delta Bytes delta
First run
Start 0 0 0 0
1st Step 27.267 27.267 17.504 17.504 250.164 250.164 249.855249.855
2nd Step 104.541 77.274 92.243 74.739 280.232 30.068 278.510 28.655
3rd Step 121.615 17.074 107.112 14.869 288.291 8.059 283.440 4.930
4th Step 144.738 23.123 128.005 20.893 293.795 5.504 288.442 5.002
21.124 21.056 26.317 23.609
Second run
Start 0 0 0
1st Step 27.210 27.210 9.534 9.534 7.402 7.402
2nd Step 104.686 77.476 16.102 6.568 11.910 4.508
3rd Step 121.765 17.079 19.972 3.870 14.636 2.726
4th Step 144.754 22.989 23.760 3.788 17.114 2.478
21.056 9.112 6.352
Result: Network Load Details APO
165.862 143.636 320.112 312.051
165.810 32.872 23.466
Map on Logonscreen
18. SAP AG 2003, Title of Presentation, Speaker Name / 18
Business Process Tested: APO Maintain Master Data
The following transaction was run through
Logon
Supply Chain Monitor Transaction: Master Data Maintain Model
Also part of the Standard Advanced Planner and Optimizer (APO)
Application Benchmark
Individual steps
1st Step -> Logon
2nd Step -> Start Transaction: Master Data Maintain
The tests are repeated once to see effects with caching
19. SAP AG 2003, Title of Presentation, Speaker Name / 19
Result: Total Number of Received Bytes APO
LAN connection WAN connection
Logon, Start Transaction
SAP GUI WTS
1st run
SAP GUI WTS
2nd run (cache)
Local SAP GUI,
both runs
177,000
149,521
314,521 322,000
30,610 23,890
0
50,000
100,000
150,000
200,000
250,000
300,000
350,000
20. SAP AG 2003, Title of Presentation, Speaker Name / 20
SAPGUI LAN
(no LSC)
SAPGUI WAN
with LSC
WTS LAN
data compress
WTS WAN
all flags
Bytes delta Bytes delta Bytes delta Bytes delta
First run
Start 0 0 0 0
1st Step 27.189 27.189 17.523 17.523 253.467253.467 250.500 250.500
2nd Step 173.314 149.125 149.521131.998 314.521 61.054 322.000 71.500
173.314 149.521 314.521 322.000
Second run
Start 0 0 0
1st Step 27.211 27.211 9.146 9.146 7.092 7.092
2nd Step 178.099 150.888 30.610 21.464 23.890 16.798
178.099 30.610 23.890
Result: Network Load Details APO
Map on Logonscreen
21. SAP AG 2003, Title of Presentation, Speaker Name / 21
Business Process Tested: APO – Planning Table
The following transaction was run through
Logon
Call Planning Table
Also part of the Advanced Planner and Optimizer (APO) Standard
Application Benchmark
Individual steps
1st Step -> Logon
2nd Step -> Call Planning Table
The tests are repeated once to see effects with caching
22. SAP AG 2003, Title of Presentation, Speaker Name / 22
Result: Total Number of Received Bytes APO
LAN connection WAN connection
Logon, Call Planning Table
SAP GUI WTS
1st run
SAP GUI WTS
2nd run (cache)
Local SAP GUI,
both runs
224,000
205,346
66,725 66,349
17,014 12,992
0
50,000
100,000
150,000
200,000
250,000
300,000
350,000
23. SAP AG 2003, Title of Presentation, Speaker Name / 23
SAPGUI LAN
(no LSC)
SAPGUI WAN
with LSC
WTS LAN
data compress
WTS WAN
all flags
Bytes delta Bytes delta Bytes delta Bytes delta
First run
Start 0 0 0 0
1st Step 27.600 27.600 17.282 17.282 33.281 33.281 36.020 36.020
2nd Step 224.090 196.490 205.346188.064 66.725 33.444 66.349 30.329
224.090 205.346 66.725 66.349
Second run
Start 0 0 0
1st Step 27.927 27.927 7.840 7.840 5.762 5.762
2nd Step 224.399 196.472 17.014 9.174 12.992 7.230
224.399 17.014 12.992
Result: Network Load Details APO
Without Map on Logonscreen
24. SAP AG 2003, Title of Presentation, Speaker Name / 24
Network Load SAPGui for Windows/Java And Citrix
BW
WTS
Backbone
50 kB (20 kB)
LAN
300 kB
LAN
APO WTS
Backbone
66 kB (13 kB)
LAN
200 kB
LAN
Data Center
25. SAP AG 2003, Title of Presentation, Speaker Name / 25
Summary
The local SAP GUI for Windows (PC installation) produces
minimal network load for data entry
The SAP GUI remains an ultra-thin client that can be used in WAN
environments
Depending on Infrastructure and Implementation following
Benefits are possible with the usage of Windows Terminal Server
Reducing network trafic while integration software applications
Rapid deployment of software applications
Easier maintenance, administration and support