1. IT Platform Selection by Economic Factors and Information Security Requirements (SAP Case Study ) 20 10 А. SHMID Doctor, Professor www.ec-leasing.ru

2. Global System Services Interpretive Information Systems EC-leasing EC-leasing Soft in Russia in USA IBM BP in Russia, USA, Germany www.ec-leasing.ru www. gs-s.com Main Focus – to decrease Total Cost of Ownership (TCO) for corporate customers by architecture consolidation and create disaster recovery and availability solutions ЕС- leasing is a Systems Integrator for Major Corporate Customers EC-leasing – 63% of Mainframe market of RF Two biggest SAP Computer Centres in RF

6. Project Steps for Selection of CC Platform for SAP based on the final CC configuration comparison Step # Conceptual levels # of elements on the level Prerequisite to go to the next level Comment 1 SAP business processes # of BPs in SAP to be located on CC # of SAP users for each BP and SAP user roles Types of SAP systems order for CC 2 SAP systems # of SAP systems to be located on CC Minimum Guaranteed SAP Capacity in SAPS per system (MGC) Logical complexity order for CC (SAP systems) 3 SAP hosts for HAS mode # of SAP hosts to be located on CC ∑ MGC for all hosts SAP capacity order for CC (in SAPS) 4 Platform logical work units for SAP host allocation (tasks, LPARs, domains) # of logical platform work units for SAP host allocation MGC for each logical Platform work unit SAP capacity order distribution for logical platform work units 5 Platform physical units for SAP capacity distribution # of servers and LPARs / domains with cores/cpu Hardware/Software order draft configuration for competing platforms Estimate TCO for competing platforms ( ∑ $ for 5 years per platform)

7. Configuration Documentation

8. AIX: IBM DB2 for z/OS Solaris : Oracle High Availability System: HAS mode Page 20 Page 2 3 Configuration Documentation – SAP Tasks

9. Configuration Documentation

10. AIX: IBM DB2 for z/OS HP-UX : Oracle Page 19 Page 2 3 Configuration Documentation – SAP Tasks High Availability System: HAS mode

12. Platform Choice Influence on TCO ( High Availability Implementation Case ) Final Configurations, Estimation and Comparison

14. Looking for Difference in Single Servers (SAP Website) www.sap.com For  same performance Sun uses 4 times more cores than p and 2 times more than HP:  3 times more power supply for the same performance;  3 times more soft cost HP Integrity Superdome IBM – Power System p6 Sun - SPARC Enterprise M9000 Product 152 530 177 950 196 570 SAPS 1,6 5 , 0 2, 52 Clock (GHz) 18 Dec 06 24 March 08 28 June 08 Date 32 64 Chips 128 64 256 Cores

16. Domain – Domain no Subdomain – Subdomain no Solaris thread EAL4+ nPAR – nPAR no vPAR – vPAR no HP-UX thread EAL4+ LPAR – LPAR EAL4+ AIX thread EAL4+ LPAR – LPAR EAL 5 zOS task EAL4+ http://www.commoncriteriaportal.org/products.html Sun HP IBM p IBM z Facilities Certificate (W U) Level Platform Existing Certificates on Common Criteria Website

17. Separate Servers yes yes yes Domain – Domain no yes yes Subdomain – Subdomain no yes yes Solaris thread EAL4+ no no Separate Servers yes yes yes nPAR – nPAR no yes yes vPAR – vPAR no yes yes HP-UX thread EAL4+ no no Separate Servers yes yes yes LPAR – LPAR EAL4+ yes yes AIX thread EAL4+ no no Separate Servers yes yes yes LPAR – LPAR EAL 5 yes yes zOS task EAL4+ yes yes http://www.commoncriteriaportal.org/products.html Sun HP IBM p IBM z Platform Platform Work Units To Be Used For Process Allocation in Parallel Virtual Environment Facilities Certificate Guaranteed Conclusions Level (С) Resource Availability (W U) Minimum ( GRM ) (GRM)

18. SAP Logical Hosts Allocation On Platform Work Units With GRM Platform Work unit with GRM Resource order per WU Max # of WU per server Max # of SAP Hosts per server Min # of core/cpu per Max # of WU on Server Min SAPS per Server/ Host(WU) IBM z z/OS task LPAR (z/OS) % of CPU group (not less than 1% for WU) 100 tasks x 16 LPAR = 1600 WU 1600 1 CPU 4 680 (0.73) IBM p LPAR (AIX,Linux) % of core group (not less than 1% for WU) 256 LPAR = 256 WU 256 4 Cores 11 062 (43.71) SUN Domain (Solaris) # of cores per domain 24 Domain = 24 WU 24 24x4=96 (1 proc - 4 cores per domain) 73 713 (3071)

19. Example To Compare Competitive CC Allocation For 78 SAP Systems To meet logical complexity (LC) for CC. Min performance for given LC is required to create testing and development landscapes N # SAP Systems LC #SAP Systems for 3 landscapes LC #SAP hosts in HAS mode # Servers for host allocation Min #Core/CPU for 2.3.4. Min # of SAPS per 2.3.4. 1 2 3 4 5 6 7 Sun Solaris (HAS) 78 234 234x7=1638 1638:24=68.25 (69) (24 - #of Sun domain) 69 Servers 1 processor min (4cores) per 1 domain 4x24x69=6624 cores 5 086 249 pAIX (HAS) 78 234 234x7=1638 1638:256=6.4 (7) (256 - #of LPAR for p) 7 Servers LPAR–0.01 proc 1 proc = 2 cores 0.01x2x256=5.12 7x6=42 cores 116 780 z/OS + pAIX (HAS) 78 234 234x3=702 234 DB hosts – z 468 App hosts – 2p 3 Servers (1z+2p) 1 CPU z 2x7=14 cores 4687+44187=48 874

20. Logical complexity: 234 systems. Performance 1 000 000 SAPS total for 3 landscapes SAPS Performance allocation for systems Min MGC for SAP system – 95 SAPS Max MGC for SAP system – 42 000 SAPS Final Configuration Comparison for Given Logical Complexity and Effective Performance 7 80% 1 245 650 1 000 000 1638 234 pAIX 1z + 5p (6) 93% 1 067 700 1 000 000 702 2334 z/OS + pAIX Min 69 Max 19% Min 5 086 249 for 4 cores on domain, varies from max 42 000 SAPS to min 95 SAPS 1 000 000 1638 234 Sun Solaris 7 6 5 4 3 2 1 Number of Servers E fficiency Factor % (4 / 5) CC performance to be purchased CC performance in SAPS in use #SAP hosts in HAS mode #SAP systems for 3 landscapes (Logical complexity ) N

21. Energy Efficiency Sun 196 570 SAPS – 256 cores IBM Power – 177 950 SAPS – 64 cores Sun uses 3 times more energy per SAPS than IBM Power Efficiency Factor for SUN = Efficiency Factor for IBM Power (64:256)x(199 570:177950)= 0.3 (30%) - single server On CC level Sun implementation will use 13 times more energy than IBM Power (15 times: z+p) 80% 1 245 650 1 000 000 100% 1 IBM Power 6% 5 086 249 1 000 000 30% 3 Sun E f f iciency Factor for CC CC performance to be purchased CC performance in SAPs in use Efficiency Factor per 1 SAPs Energy per 1 SAPs

22. Computer Centre Characteristics : Expandability – logical complexity – up to 300 systems Scalability - up to 1 0 00 000 SAPS efficient performance Availability : Downtime With IBM GDPS – less than 10 minutes a year. BUT depends on WU allocation Concept : Centralized Architecture of Computer Centre with Virtualization on System z – Power Basis zEnterprize At the expandability level - up to 300 SAP Systems – initial configuration equals to final configuration ( 1z + 5p ) Power Rating according to Gartner Group: №2 z10 Rating according to Gartner Group : №1 Virtual Net of Virtual Application Servers Virtual Net of Virtual Application Servers IBM Cluster EAL5 Up to 60 Base Servers EAL5 Power EAL4 Power EAL4 Up to 256 Application Servers according to EAL 4 ( on each pSeries) Virtual Net of Virtual Data Base Servers

24. Thank you for your attention !