Anda di halaman 1dari 37

Best Practice Design for SAP Landscapes

Manfred Engelbart, SAP Solution Infrastructure Architect

2010 IBM Corporation

IBM SAP Alliance

Topics

SAP on IBM i Reference Architecture IBM Rule of Thumbs for SAP Sizing Appendix: Calculation Example

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

Best Practice Design for SAP Landscapes

SAP on IBM i Reference Architecture

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

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

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

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

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

Operating System Options

IBM i Standard Edition IBM i Enterprise Edition IBM i Express Edition

: Database oriented SAP workload (ERP, CRM, BW, SCM) : 5250 oriented workload : Application Server oriented workload

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

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
7 15.04.2010 Template Documentation 2010 IBM Corporation

IBM SAP Alliance

Running SAP technology stacks on IBM i

IBM Power Systems

ABAP, JAVA and Dual Stack run on IBM i Multiple SAP systems may run in an LPAR
LPAR

ABAP

JAVA

DUAL STACK

Adobe native Library


2010 IBM Corporation

15.04.2010

Template Documentation

IBM SAP Alliance

Adobe Document Services (ADS) and SAP on IBM i


Windows Server

IBM Power Systems

ADS

ABAP

JAVA

Any ABAP or JAVA component may use ADS if and when required

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

Standalone server KOBI approach for ERP only


Windows Server
Adobe Document Server

IBM Power Systems POWER7 IBM i 7.1

ERP Production PRD

DB2 for IBM i

Development & Test for ERP DEV QAS Solution Manager

10

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

Standalone server advanced approach for ERP only


Windows Server
Adobe Document Server

IBM Power Systems POWER7 IBM i 7.1

LPAR1: ERP Production PRD


DB2 for IBM i

IBM i Applications

LPAR2: Development & Test for ERP DEV QAS Solution Manager

DB2 for IBM i

IBM i Test Applications

11

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

Systems Management and Monitoring Options


IBM Power Systems

DEV

Solution Manager

QAS

Windows Server

IBM Systems Director

SAP Solution Manager: Monitor and Manage SAP Applications


PRD

IBM Systems Director: Monitor and Manage POWER Systems hw


2010 IBM Corporation

12

15.04.2010

Template Documentation

IBM SAP Alliance

Standalone Server approach for SAP All in One


Windows Server
Adobe Document Server

IBM Power Systems POWER7 IBM i 7.1

SAP Business Objects (optional)

LPAR1: ERP and CRM Production PRD


DB2 for IBM i

IBM i Applications

LPAR2: BW Production PRD


DB2 for IBM i

IBM i Applications

LPAR3: Development & Test for ERP, CRM, BW DEV QAS Solution Manager IBM i Test Applications

DB2 for IBM i

13

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

Business Objects and SAP on IBM i


Windows Server

IBM Power Systems

Business Objects

LPAR1 ERP

LPAR2 BW

LPAR3
DB2 for IBM i

DB2 for IBM i is a SAP Business Objects certified data Adobe native source Library
2010 IBM Corporation

14

15.04.2010

Template Documentation

IBM SAP Alliance

Advanced Standalone Server Approach (SAP Business Suite)


IBM Power Systems POWER7 IBM i 7.1 Windows Server
Adobe Document Server

SAP Business Objects

LPAR1: Production ERP SCM MDM IBM i Applications

DB2 for IBM i

APO Live Cache

LPAR2: Production BW
DB2 for IBM i

Linux Server
BW Accelerator

LPAR3: Development & Test for ERP, SCM, BW DEV QAS Solution Manager IBM i Test Applications

DB2 for IBM i

15

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

High Availability Options

Local Mirror
DB2 for IBM i Indep enent ASP Active copy

DB Replication

Local iASP

LP A R1 : Pr od uct ion

Geo Mirror

External iASP

Decision Criteria Recovery Times Distance between Systems Logical or Physical Replications

16

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

HA Example for Advanced SAP Business Suite Implementations


IBM Power Systems POWER7 IBM i 7.1 IBM Power Systems POWER7 IBM i 7.1

LPAR1: Production ERP PI EP

Geographic Mirroring
DB2 for IBM i

LPAR 1: Backup ERP PI EP

DB2 for IBM i

LPAR 2: BW Production
DB2 for IBM i

SAP components with different workload profile in different LPARs DEV/QA/TEST ca. 30% of production environment

LPAR 3: Development & Test for: ERP PI EP Solution Manager

DB2 for IBM i

17

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

Best Practice sizing for SAP Landscapes

IBM Rule of Thumbs for SAP Sizing

18

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

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

19

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

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: Memory: Disk Space: I/O Perf.: RoT, User Based Sizing (SAP QS), Volume Based Sizing (SAP QS Throughput Sizing) RoT RoT plus SAP QS Results RoT

20

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

CPU Sizing for frequently used SAP Components

SAP Comp. ERP

Common Sizing Method


- RoT

- SAP Quicksizer - User Based Sizing - Standard-Configs

CRM BW EP (Portal) PI
(ehem. XI)

- SAP - SAP

Quicksizer User Based Sizing

Quicksizer User Based Sizing (rough estimation) - Web-Reporting -> up to 80% of ABAP Load -> JAVA
- SAP - SAP

Quicksizer User Based Sizing

Quicksizer Volume Based Sizing - based on Number and size of messages


- T-shirt

Solution Manager

Sizing (S/M/L)

21

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

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

22

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

CPU Throughput, ECC6.0, Unicode 1/3

CPU POWER5

Mhz 1650 1900

SAPS/Core 1000 1160 1160 1410 1530

POWER5+

1900 2200 2300

23

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

CPU Throughput, ECC6.0, Unicode 2/3

CPU POWER6

Mhz 3500 3600 4200 4400 4700 5000

SAPS/Core 1500-1600 1650 1700-1900 2000 1850-2140 2160-2330

24

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

CPU Throughput, ECC6.0, Unicode 3/3

CPU POWER7

Nominal Mhz 3300 3000 3300 3550 3100 3500 3860 4100

Turbo Mhz 3510 3200 3640 3860 3300 3800 4100 4100

SAPS/Core 2400 2090 2240 2360 2190 2490 2590 2980

25

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

Memory RoT (ABAP)


POWER5 POWER5+ POWER6 POWER7
at least 10 GB / Core at least 12 GB / Core at least 16 GB / Core 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

26

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

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

27

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

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 medium installations large installations

(up to 1,000 SAPS) (up to 5,000 SAPS) (greater than 5,000 SAPS)

50 GB 70 GB 150 GB

28

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

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 2,000 SAPS for BW 1,500 SAPS for EP

approx. 3,000 I/O approx. 1,200 I/O approx. 300 I/O

approx. 30 Drives approx. 12 Drives approx. 3 Drives

29

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

BACKUP SLIDES

30

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

Best Practice sizing for SAP Landscapes

Calculation Example

31

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

Example SAP Landscape Sizing


Total SAPS ABAP Java Sizing Methodology

ERP BW PI EP Sol. Mgr. Total

8,000 3,600 2,000 2,000 500 16,100

8,000 2,000 1.600 2,000 2,000 500 10,000 6,100

SAP QS (User) SAP QS SAP QS (Volume) SAP QS (User) T-Shirt

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.

32

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

Example SAP CPU Sizing incl. XSM (plus 10%)


Total SAPS ERP PI EP Sol. Mgr. BW Total 8,000 2,000 2,000 500 3,600 15,500 1,250 XSM 800 200 200 50 Total SAPS 8,800 2.200 2,200 550 3,600 16,750 Nbr of cores (2400 SAPS/Core) 3.66 0.91 0.91 0.23 1.5 7.21

33

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

Example Lets Review The Memory Mapping


SAP ERP ABAP 8,000 SAPS / 2,400 = 3.66 CPUs * 16 GB SAP BI ABAP 2,000 SAPS / 2,400 = 0.83 CPUs * 16 GB Java 1,600 SAPS: 3 GB Basis plus 4x3 GB SAP PI Java 2,000 SAPS: 3 GB Basis + 4x3 GB SAP EP Java 2,000 SAPS: 3 GB Basis +3x3 GB SAP Sol. Manager Java 3 GB Basis + 1x3 GB in total equals (7.21 Cores)
34 15.04.2010 Template Documentation

58 GB

13 GB 15 GB

15 GB

12 GB

6 GB 119 GB 16.5 GB (per core)


2010 IBM Corporation

IBM SAP Alliance

Example - I/O Performance


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 for 15k rpm disks 100 I/O per second Example 10,000 SAPS for ERP, PI 3,600 SAPS for BW 2,500 SAPS for EP, SolMan Total

approx. 4,000 I/O approx. 2,160 I/O approx. 500 I/O

approx. 40 Drives approx. 22 Drives approx. 5 Drives approx. 63 Drives

35

15.04.2010

Template Documentation

2010 IBM Corporation

IBM SAP Alliance

Example Final Layout for LPARs


# of Cores Memory (GB) Drives

LPAR0 (ERP, PI, EP, SolMan) Server PROD LPAR1 (XSM) LPAR2 (BW) LPAR3 (Dev/QA) Server Backup/BW/DEV

5.71 6 1 1.5 2.3 6(5)

ABAP: 58 JAVA: 33* 96 16 ABAP: 13 JAVA: 15 52 96

45 Drives (12/33) ** 45 45 Drives (12/33) ** 22 20 *** 132

Remarks: (*) Max. For JAVA-Pool, best praxis approach: 20-30 GB) (**) Ratio ASP1 : IASP = ca. 1:3 (***) Prefer high volume drives
36 15.04.2010 Template Documentation 2010 IBM Corporation

IBM SAP Alliance

Example Final Layout of System Landscape


Basis: IBM Power 750 server, 3300/3510 MHZ
XSM

LPAR0 DBSchema Library

LPAR 1 SOL mgr

LPAR 2

LPAR 3

ERP

PI

EP

ERP

PI Sol Mgr.

BW

DEV QA Test

EP
Journal IBM i 6 Cores 96 GB Mem. Disk ASP1 12 Drives IASP, 33 Drives 0,1 IBM i

IBM i 0,1

IBM i

1 Core 16 GB Mem.
ASP1 12 D. IASP 33 D.

2 Core 28 GB Mem. 22 Drives

3 Cores 52 GB Memory 20 Drives

Storage internal or external

Storage internal or external Backup-Copy

Production

Production

QAS + DEV

SAP components with different workload profile in different LPARs DEV/QA/TEST ca. 30% of production environment
37 15.04.2010 Template Documentation 2010 IBM Corporation