06 ibm best practice design
TRANSCRIPT
© 2010 IBM Corporation
Best Practice Design for SAP Landscapes
Manfred Engelbart, SAP Solution Infrastructure Architect
© 2010 IBM Corporation
IBM SAP Alliance
2 Template Documentation15.04.2010
Topics
� SAP on IBM i Reference Architecture
� IBM Rule of Thumbs for SAP Sizing
� Appendix: Calculation Example
© 2010 IBM Corporation
IBM SAP Alliance
3 Template Documentation15.04.2010
Best Practice Design for SAP Landscapes
SAP on IBM i Reference Architecture
© 2010 IBM Corporation
IBM SAP Alliance
4 Template Documentation15.04.2010
Reference architecture considerations
� Solution Components
– Server and Operation System Options
– Storage Options
– High Availability Options
– Systems Management and monitoring options
– Business Objects and SAP on i
– Adobe Document Server and SAP on i
� SAP Solutions Landscapes
– Standalone server approach for ERP only (Kobi Based Architecture)
– Standalone Server approach for SAP All in One
– Advanced Standalone Server Approach (SAP Business Suite)
– HA Approach for Advanced SAP Business Suite Implementations
© 2010 IBM Corporation
IBM SAP Alliance
5 Template Documentation15.04.2010
Server Footprint Options
� Standalone Server
– Integrated and Simple in one Server
– Greater Scalability
– Multiple Consolidation Options
– Direct Attached Storage
– Minimum Administration Efforts
� Blade Server
– Consolidate multiple small systems
– Consolidate Windows and POWER
– Requires Virtual I/O Server for Storage and Tape Support
– Limited internal storage for Blade Center H
– External storage required for Blade Center S
– Extend existing Blade system strategy
© 2010 IBM Corporation
IBM SAP Alliance
6 Template Documentation15.04.2010
Operating System Options
� IBM i Standard Edition : Database oriented SAP workload (ERP, CRM, BW, SCM)
� IBM i Enterprise Edition : 5250 oriented workload
� IBM i Express Edition : Application Server oriented workload
© 2010 IBM Corporation
IBM SAP Alliance
7 Template Documentation15.04.2010
Storage Options
� Internal Storage Focus
– Maximum Integration
– Minimum Administration
� External Storage Focus
– Heterogeneous Environments
– Advanced Storage Managment Functions
• Flashcopy
• Geographic Mirroring
� Virtualized Storage Focus
– Blade Center H Support
– Extended Storage Options
• SVC attachement
• DS4k
© 2010 IBM Corporation
IBM SAP Alliance
8 Template Documentation15.04.20108
Running SAP technology stacks on IBM i
Adobe native Library
IBM Power Systems
ABAP
DUAL STACK
JAVA
LPAR
• ABAP, JAVA and Dual Stack run on IBM i
• Multiple SAP systems may run in an LPAR
© 2010 IBM Corporation
IBM SAP Alliance
9 Template Documentation15.04.20109
Adobe Document Services (ADS) and SAP on IBM i
IBM Power Systems
JAVA
ABAP
Windows
Server
ADS
Any ABAP or JAVA component may use ADS if and when required
© 2010 IBM Corporation
IBM SAP Alliance
10 Template Documentation15.04.2010
Standalone server KOBI approach for ERP only
IBM Power Systems
POWER7
IBM i 7.1
ERP Production• PRD
Development & Test for ERP• DEV• QAS
Solution Manager
DB2 for IBM i
Adobe Document Server
Windows
Server
© 2010 IBM Corporation
IBM SAP Alliance
11 Template Documentation15.04.2010
Standalone server advanced approach for ERP only
IBM Power Systems
POWER7
IBM i 7.1
LPAR1: ERP Production• PRD
• IBM i Applications
LPAR2: Development & Test for ERP• DEV• QAS• Solution Manager
• IBM i Test Applications
DB2 for IBM i
DB2 for IBM i
Adobe Document Server
Windows
Server
© 2010 IBM Corporation
IBM SAP Alliance
12 Template Documentation15.04.2010
IBM Power Systems
12
Systems Management and Monitoring Options
PRD
DEVWindows
ServerQAS
IBM Systems Director
SAP Solution Manager:Monitor and Manage SAP Applications
IBM Systems Director:Monitor and Manage POWER Systems hw
Solution Manager
© 2010 IBM Corporation
IBM SAP Alliance
13 Template Documentation15.04.2010
IBM Power Systems
POWER7
IBM i 7.1
Standalone Server approach for SAP All in One
LPAR1: ERP and CRM Production
• PRD
• IBM i Applications
DB2 for IBM i
LPAR2: BW Production
• PRD
• IBM i Applications
DB2 for IBM i
LPAR3: Development & Test for ERP, CRM, BW
• DEV
• QAS
• Solution Manager
• IBM i Test Applications
DB2 for IBM i
Adobe Document Server
Windows
Server
SAP Business Objects(optional)
© 2010 IBM Corporation
IBM SAP Alliance
14 Template Documentation15.04.201014
Business Objects and SAP on IBM i
Adobe native Library
IBM Power Systems
LPAR3
LPAR2
LPAR1
ERP
Windows
Server
Business Objects
DB2 for IBM i
BW
DB2 for IBM i is a SAP Business Objects certified data source
© 2010 IBM Corporation
IBM SAP Alliance
15 Template Documentation15.04.2010
IBM Power Systems
POWER7
IBM i 7.1
Advanced Standalone Server Approach (SAP Business Suite)
LPAR1: Production
• ERP
• SCM
• MDM
• IBM i Applications
DB2 for IBM i
LPAR2: Production
• BW DB2 for IBM i
LPAR3: Development & Test for ERP, SCM, BW
• DEV
• QAS
• Solution Manager
• IBM i Test Applications
DB2 for IBM i
Adobe Document Server
Windows
Server
SAP Business Objects
APO Live Cache
BW Accelerator
Linux
Server
© 2010 IBM Corporation
IBM SAP Alliance
16 Template Documentation15.04.2010
High Availability Options
LP
A
R1:
Pr
od
uct
ion
DB2
for IBM i
Indep
enent
ASP
Active copy
Local iASP
External iASP
Local Mirror
Geo Mirror
DB Replication
Decision Criteria• Recovery Times• Distance between Systems• Logical or Physical Replications
© 2010 IBM Corporation
IBM SAP Alliance
17 Template Documentation15.04.2010
IBM Power Systems
POWER7
IBM i 7.1
IBM Power Systems
POWER7
IBM i 7.1
HA Example for Advanced SAP Business Suite Implementations
LPAR1: Production
• ERP
• PI
• EP DB2 for IBM i
LPAR 2: BW Production
DB2 for IBM i
LPAR 3: Development & Test for:• ERP• PI• EP
Solution Manager
DB2 for IBM i
DB2 for IBM i
� SAP components with different workload profile in different LPAR‘s� DEV/QA/TEST ca. 30% of production environment
Geographic Mirroring LPAR 1: Backup
• ERP
• PI
• EP
© 2010 IBM Corporation
IBM SAP Alliance
18 Template Documentation15.04.2010
Best Practice sizing for SAP Landscapes
IBM Rule of Thumbs for SAP Sizing
© 2010 IBM Corporation
IBM SAP Alliance
19 Template Documentation15.04.2010
Rule of Thumb Sizing – updates, news
� CPU-Sizing:
– SAPS values based on Unicode implementation
– SAPS RoT for POWER7 based models
� Memory-Sizing:
– POWER7 memory requirements
– JAVA memory requirements
� I/O infrastructure sizing:
– First RoT assumptions for SSD-disk sizing
© 2010 IBM Corporation
IBM SAP Alliance
20 Template Documentation15.04.2010
Best Practice Sizing Methodologies
� SAP Quicksizer (User and Quantity Based):
– CPU
– Capacity
� IBM Rule of Thumbs:
– CPU
– Memory
– Capacity
– I/O-Performance
� Combination of Quicksizer and Rule of Thumbs
– CPU: RoT, User Based Sizing (SAP QS), Volume Based Sizing (SAP QS Throughput Sizing)
– Memory: RoT
– Disk Space: RoT plus SAP QS Results
– I/O Perf.: RoT
© 2010 IBM Corporation
IBM SAP Alliance
21 Template Documentation15.04.2010
CPU Sizing for frequently used SAP Components
- T-shirt Sizing (S/M/L)Solution
Manager
- SAP Quicksizer – Volume Based Sizing- based on Number and size of messages
PI (ehem. XI)
- SAP Quicksizer – User Based SizingEP (Portal)
- SAP Quicksizer – User Based Sizing (rough estimation)- Web-Reporting -> up to 80% of ABAP Load -> JAVA
BW
- SAP Quicksizer – User Based SizingCRM
- RoT- SAP Quicksizer - User Based Sizing- Standard-Configs
ERP
Common Sizing MethodSAP
Comp.
© 2010 IBM Corporation
IBM SAP Alliance
22 Template Documentation15.04.2010
Rules of Thumb for SAPS (Unicode)
� RoT when not using the SAP QS
– 1 concurrent active ERP user = 10 SAPS
– 1 concurrent active CRM, BW user = 20 SAPS
ASCII = Unicode minus 20% CPU capacity.
Named User= 100%,
Example: 100
Logged On User= 80% of
Named User Bsp: 80
Concurrent Active User= 65% of Logged On User,
Example: 80 * 0,65 = 52
© 2010 IBM Corporation
IBM SAP Alliance
23 Template Documentation15.04.2010
CPU Throughput, ECC6.0, Unicode – 1/3
15302300
14102200
11601900POWER5+
11601900
10001650POWER5
SAPS/CoreMhzCPU
© 2010 IBM Corporation
IBM SAP Alliance
24 Template Documentation15.04.2010
CPU Throughput, ECC6.0, Unicode – 2/3
1850-21404700
2160-23305000
20004400
1700-19004200
16503600
1500-16003500POWER6
SAPS/CoreMhzCPU
© 2010 IBM Corporation
IBM SAP Alliance
25 Template Documentation15.04.2010
CPU Throughput, ECC6.0, Unicode – 3/3
298041004100
259041003860
249038003500
219033003100
236038603550
224036403300
209032003000
240035103300POWER7
SAPS/CoreTurbo MhzNominal MhzCPU
© 2010 IBM Corporation
IBM SAP Alliance
26 Template Documentation15.04.2010
Memory RoT (ABAP)
� POWER5 at least 10 GB / Core
� POWER5+ at least 12 GB / Core
� POWER6 at least 16 GB / Core
� POWER7 at least 16 GB / Core
Remarks:
The values given are valid for 1 SAP instance. Each additional SAP instance will require at least 3 GB more memory
The values given are valid for a SAP typical load
© 2010 IBM Corporation
IBM SAP Alliance
27 Template Documentation15.04.2010
Memory RoT (Java)
� Java Basic Setup 3 GB
� Guideline for additional memory requiremends depending on SAPS value of Java application environments (first assumptions, subject to change).
Additional 3 GB Memory per:
– PI: approx. 600 SAPS (high memory footprint for large message sizes)
– BW: approx. 400 SAPS
– EP: approx. 800 SAPS
© 2010 IBM Corporation
IBM SAP Alliance
28 Template Documentation15.04.2010
Disk Space RoT
� Basis: 50 GB for OS, 100 GB for ‚empty‘ SAP system
� Use SAP QS results for capacity growth
– User based sizing: per year
– Throughput sizing: per retention period
� SAP QS results assumes single byte encoding, for Unicode apply approx. +50%
� temp Space
small installations (up to 1,000 SAPS) 50 GB
medium installations (up to 5,000 SAPS) 70 GB
large installations (greater than 5,000 SAPS) 150 GB
© 2010 IBM Corporation
IBM SAP Alliance
29 Template Documentation15.04.2010
I/O calculation
� Number of I/O per second required
– 0.4 I/O per second / SAPS (ERP, PI)
– 0.6 I/O per second / SAPS (BW)
– 0.2 I/O per second / SAPS, (assumption for SAP Components with low I/O requirements, e.g. EP, SolMan)
� I/O throughput
– 100 I/O per second (15k RPM drives)
– >1000 I/O per second (SSD drives, predominantly read)
� Example (15k RPM drives)
– 7,500 SAPS for ERP, PI approx. 3,000 I/O approx. 30 Drives
– 2,000 SAPS for BW approx. 1,200 I/O approx. 12 Drives
– 1,500 SAPS for EP approx. 300 I/O approx. 3 Drives
© 2010 IBM Corporation
IBM SAP Alliance
30 Template Documentation15.04.2010
BACKUP SLIDES
© 2010 IBM Corporation
IBM SAP Alliance
31 Template Documentation15.04.2010
Best Practice sizing for SAP Landscapes
Calculation Example
© 2010 IBM Corporation
IBM SAP Alliance
32 Template Documentation15.04.2010
Example – SAP Landscape Sizing
‚T-Shirt‘500500Sol. Mgr.
6,10010,00016,100Total
SAP QS (User)2,0002,000EP
SAP QS (Volume)2,0002,000PI
SAP QS1.6002,0003,600BW
SAP QS (User)8,0008,000ERP
Sizing MethodologyJavaABAPTotal SAPS
Additional requirements:
- 2 server concept required: primary production and Backup/Dev,QA- SAP BW in seperate LPAR (no HA required)- Local HA Cluster (XSM) for ERP, PI, EP, Sol.Mgr.
© 2010 IBM Corporation
IBM SAP Alliance
33 Template Documentation15.04.2010
Example – SAP CPU Sizing incl. XSM (plus 10%)
0.2355050500Sol. Mgr.
7.2116,7501,25015,500Total
1.53,6003,600BW
0.912,2002002,000EP
0.912.2002002,000PI
3.668,8008008,000ERP
Nbr of cores
(2400 SAPS/Core)
Total
SAPS
XSMTotal SAPS
© 2010 IBM Corporation
IBM SAP Alliance
34 Template Documentation15.04.2010
Example – Let‘s Review The Memory Mapping
� SAP ERP
– ABAP 8,000 SAPS / 2,400 = 3.66 CPUs * 16 GB 58 GB
� SAP BI
– ABAP 2,000 SAPS / 2,400 = 0.83 CPUs * 16 GB 13 GB
– Java 1,600 SAPS: 3 GB Basis plus 4x3 GB 15 GB
� SAP PI
– Java 2,000 SAPS: 3 GB Basis + 4x3 GB 15 GB
� SAP EP
– Java 2,000 SAPS: 3 GB Basis +3x3 GB 12 GB
� SAP Sol. Manager
– Java 3 GB Basis + 1x3 GB 6 GB
� in total 119 GB
� equals (7.21 Cores) 16.5 GB (per core)
© 2010 IBM Corporation
IBM SAP Alliance
35 Template Documentation15.04.2010
Example - I/O Performance
� NumberNumberNumberNumber of I/O per second of I/O per second of I/O per second of I/O per second requiredrequiredrequiredrequired– 0.4 I/O per second / SAPS (ERP, PI)– 0.6 I/O per second / SAPS (BW)– 0.2 I/O per second / SAPS, (assumption for SAP Components with low I/O
requirements, e.g. EP, SolMan)
� I/O I/O I/O I/O throughputthroughputthroughputthroughput for 15k for 15k for 15k for 15k rpmrpmrpmrpm disksdisksdisksdisks– 100 I/O per second
– Example– 10,000 SAPS for ERP, PI approx. 4,000 I/O approx. 40 Drives– 3,600 SAPS for BW approx. 2,160 I/O approx. 22 Drives– 2,500 SAPS for EP, SolMan approx. 500 I/O approx. 5 Drives
Total approx. 63 Drives
© 2010 IBM Corporation
IBM SAP Alliance
36 Template Documentation15.04.2010
Example – Final Layout for LPAR‘s
45966Server PROD
20 ***522.3LPAR3 (Dev/QA)
132966(5)Server Backup/BW/DEV
22ABAP: 13
JAVA: 15
1.5LPAR2 (BW)
45 Drives (12/33) **161LPAR1 (XSM)
45 Drives (12/33) **ABAP: 58
JAVA: 33*
5.71 LPAR0 (ERP, PI, EP, SolMan)
DrivesMemory
(GB)
# of Cores
Remarks:(*) Max. For JAVA-Pool, best praxis approach: 20-30 GB)(**) Ratio ASP1 : IASP = ca. 1:3(***) Prefer high volume drives
© 2010 IBM Corporation
IBM SAP Alliance
37 Template Documentation15.04.2010
0,1
Example – Final Layout of System LandscapeBasis: IBM Power 750 server, 3300/3510 MHZ
ERP
Disk
LPAR0
IBM i
Production
PI
0,1
ERP
IBM i
ASP1 12 D.
LPAR 1
BW
IBM i
ProductionBackup-Copy
DEV
IBM i
QA Test
20 Drives
QAS + DEV
XSM
Storage internal or external
Journal
ASP1 12 Drives IASP, 33 Drives 22 Drives
Storage internal or external
6 Cores
96 GB Mem.
2 Core
28 GB Mem.
3 Cores
52 GB Memory
SOL
mgrEP
DB-
Schema
Library PI
IASP 33 D.
EPSol
Mgr.
LPAR 2 LPAR 3
�
� SAP components with different workload profile in different LPAR‘s� DEV/QA/TEST ca. 30% of production environment
1 Core
16 GB Mem.