WIXLIB

Technical Architecture for SAP HANAA Transition to SAP HANA InitiativeSAP Active Global Support – IT-Planning

DisclaimerThis presentation outlines our general product direction and should not be relied on inmaking a purchase decision. This presentation is not subject to your licenseagreement or any other agreement with SAP. SAP has no obligation to pursue anycourse of business outlined in this presentation or to develop or release anyfunctionality mentioned in this presentation. This presentation and SAP's strategy andpossible future developments are subject to change and may be changed by SAP atany time for any reason without notice. This document is provided without a warrantyof any kind, either express or implied, including but not limited to, the impliedwarranties of merchantability, fitness for a particular purpose, or non-infringement.SAP assumes no responsibility for errors or omissions in this document, except ifsuch damages were caused by SAP intentionally or grossly negligent. 2013 SAP AG or an SAP affiliate company. All rights reserved.2

AgendaTransition to SAP HANATransition to SAP HANA - SAP AGS General OfferingTechnical Architecture for SAP HANAPlanning WorkshopDelivery Model

Having data is not enough!Are You A Real-Time Business?Win CustomersDeliver InnovationWill my systems deliver realtime performance forcustomers?How are products/servicesdoing vs. their competition?Which customer profiles aresuitable for loyalty rewards?Track complaints from callcenters and social data in realtime?How dynamic is your customersegmentation strategy?Where else is this part used inmy company? 2013 SAP AG or an SAP affiliate company. All rights reserved.Drive ExcellenceIT Delivers ahead of businessHow can you predict supplychain disruptions ahead?How do suppliers rank by cost,quality and timeliness?How is my “on-time/in full”delivery rate by customer?4

SAP AGS Value Based Delivery for SAP HANAAddressing the Challenges to Support the OpportunityThe OpportunityThe ChallengeThe OfferingRun Better – Run yourBest-Run Business onSAP HANACommon Questions Related tothe Adoption of SAP HANA SAP Solution Manager BasedMethodology and SAP AGSEngineering ServiceUnified and seamlessly integratedapplication and database stackWill the new platform fulfill theperformance requirements?Simplified maintenanceHow will SAP HANA fit into theexisting infrastructure?Effective end-to-end operationssupportHolistic approach, covering allphases and aspects of a migrationprojectAddress the related challengesproactivelyReduced TCOWhat does it mean for the operationsteam?Completely new possibilities withSAP HANAHow to minimize business downtimefor the transition?Apply best practices andexperiences from supporting the topcompaniesWhat is the project duration, relatedefforts and risks?Make a transition to SAP HANAsafe, effective and predictable 2013 SAP AG or an SAP affiliate company. All rights reserved.5

Support for the Transition to the SAP HANA Cloud PlatformBig PictureDecision Making Help customers to comprehensivelydefine strategic direction Understand of the value of SAP HANAcloud platform Ensure that HANA platform capabilitiesprovide benefits in future strategy“SAP CloudPlatform poweredby HANA” WorkshopHigh-level planningRoadmap definition Define a reasonable adoptionroadmap – sequence of systems andprojects – reflecting customerpriorities (customer-specific businessbenefits from SAP HANA) andboundary conditions (size, HA/DRrequirements, release dates, furtherprojects, .)Concrete Planning ofTransition Project(s) Define a concrete project for thetransition of one or multiple systemsto HANAmigration methods, projectapproach, system landscape, role ofMaxAttention, . 2013 SAP AG or an SAP affiliate company. All rights reserved.“SAP HANA PlatformAdoption Roadmap” WorkshopESRV Transition to SAP HANA“Migration to SAP HANA” Planning Workshop (by system /Cluster of systems)“Technical Architecture for SAPHANA” – Planning WorkshopWork streams: Architecture &Infrastructure Migration & Test Performance &Scalability Operations Readiness6

AgendaTransition to SAP HANATransition to SAP HANA - SAP AGS General OfferingTechnical Architecture for SAP HANAPlanning WorkshopDelivery Model

Designing the Technical System Landscape for SAP HANAApproachObjective Develop a technical architecture and ITInfrastructure concept for SAP solutionsbased on SAP HANA, consideringcustomer’s boundary conditions.Data CenterStrategyFlexibility / eral SAPTechnicalArchitectureSizingApproachIntroduction of typical architecture and landscapeoptionsDiscussion of design aspects and definition oftechnical architecture building blocks.Major topics:– General SAP technical architecture– Availability SLAs, DC strategy & HA/DRarchitectureTechnical Architecture forSAP, OS, Virtualization( � IT infrastructure architecture– Scalability and load balancing– Software change management landscapeJoint assessment of options according agreed set ofevaluation criteria. 2013 SAP AG or an SAP affiliate company. All rights reserved.Software ChangeManagementLandscape8

Technical Architecture for SAP HANADelivery ModelThe Technical Architecture for SAP HANA offering is delivered as a flexiblepackage consisting ofThe methodology and content implemented in SAP Solution ManagerFocus on technical architecture of SAP HANA as well as the SAP application serverlayerBest Practices and guidelines for each of the tasksTemplates for essential process stepsOnsite services: Technical Architecture for SAP HANA – Planning WorkshopTailored to the concrete customer situationDelivered as independent workshop or in the context of other Transition to HANArelated service offeringsDelivery model can be tailored in a flexible way to the concrete customer situation(partners, division of work, priorities in the project, .) 2013 SAP AG or an SAP affiliate company. All rights reserved.9

Technical Architecture for SAP HANASAP Solution Manger RoadmapSAP Solution Manager RoadmapFocus AreasTechnical Architecture for SAP HANA– Scalability– HANA appliance, cloud and storageoptions– HA/DR with SAP HANA– PRD and non-PRD HANA solutionlandscapeTechnical Architecture for SAPApplication Server layer– Sizing and scalability of SAP SolutionLandscape– Server Platform and private cloud options– HA/DR for SAP application servers 2013 SAP AG or an SAP affiliate company. All rights reserved.10

AgendaTransition to SAP HANATransition to SAP HANA - SAP AGS General OfferingTechnical Architecture for SAP HANAPlanning WorkshopDelivery Model

Technical Architecture for SAP HANAAreas in planning workshopAreasHANA Landscape01: Current andplanned SAPLandscape System landscape, (HW, size, DB/OS, Virtualization, DC, Mid- and long term strategy (mergers and acquisitions, business growth,consolidation, new applications) On-Premise – On Demand How does HANA complement theSAP landscape What is the future HANA vision HANA solutions (business driver’s)SAP Application Server Landscape Cloud definitionMajor building blocks (Application layer, HANA Platform Layer, Storage Layer)Architecture of the building blocksSAP HANA as future platform in private cloud03: ArchitectureOverview HANA Architecture Appliance Model HANA solutions04: Sizing,Scalability,Performance Source and target system based on workload analysis (performance baseline insource system, migration to HANA, resizing, ) Sizing methodology and approaches Performance and scalability 2013 SAP AG or an SAP affiliate company. All rights reserved. Overview on currentlandscape Future plans, assessment ofchange and potential risks HW Platforms, virtualization, sizes, setup(2tier, 3tier, ), OS’s SAP solution landscape - technical design(documents like TIC report, EWA )02: SAP HANAPlatform in thePrivate Cloud HANA sizing for various HANAscenarios Scale out, Scale up options NLS solutions Capacity planning & PerformanceResults SAP landscape (architecture, deploymentoptions, ) Solutions, instance structure, Size of current systems (core systems). Scalability behavior of single systems. Capacity planning Understanding of futurevision of SAP HANAplatform in private cloud Introduction into specificarchitecture topic Presentation of architectureoptions which are alreadyclear from the scoping Required capacity (& futureoutlook) and scalabilityassessment Assessment of qualitativestate of the systems (documentation ofperformance-criticalbusiness areas)12

Technical Architecture for SAP HANAAreas in planning workshopAreasHANA Landscape05: Technicalplatformoptions andarchitecture Cloud strategy (private, ) Boundary conditions06: HighAvailability /DisasterRecovery /Backup &Restore Single or scale out Scalability options SAP HANA Tailored DatacenterIntegration concept HANA in the cloud Virtualization Different HANA partner solutionsSAP Application Server Landscape Virtualization (architecture for SAP, basictechnical configuration) Server platform (UNIX / X86) Decision criteria to evaluate and assessthe options Storage SAP AS architecture (basic technicalconfiguration) Scalability, load distribution/balancing.Availability classification and requirements (RPO / RTO)Error categoriesDC StrategyLandscape aspects to backup/recoveryBusiness aspects High Availability and DisasterRecovery capabilities provided bythe SAP HANA platform DR in the cloud or on non-PRD Backup and recovery solutions andintegration into existing backupsolutions provided by partners 2013 SAP AG or an SAP affiliate company. All rights reserved.Results Architectural outline of theoptions Description of the options Assessment along thedecision criteria of theoptions Basic technicalconfiguration based on bestpractices expected futuresize (deployment options) Decision on required HA /DR / backup / restoretechnology and architectureof entire solution stackincluding HANA Options for SAP AS (ENQ replication, )and classical DB’s (replicationmechanisms, data consistency, ) Integration of solutions into the existingCustomer business continuity concept (HAclusters, HA with virtualization, )13

Technical Architecture for SAP HANAAreas in planning workshopAreasHANA Landscape07: PRD andnon-PRD SAPSystemlandscape High-level Software change management (non-PRD landscape, use cases, ) Number, size, of non-PRD Data quality in non-PRD (QA, )08: FuturePlanning HANA options for non-PRD systems HANA stacking options (MCOD,multi-SID, Virtualization)SAP Application Server Landscape Stacking options (if applicable) SAP system landscape platform usage anddistribution (virtualization, server platform,.)Project setupRoles and responsibilitiesPartner relationships (HW, hosting partner, implementation, )Risks collection 2013 SAP AG or an SAP affiliate company. All rights reserved.Results Complete Picture of SAPsystem mapping to serversplatforms HA DR backup technology RZ setup Next Steps Roles and responsibilitiesplan14

Scalability, Sizing and PerformanceOverview and Procedure for HANA SizingPreparationSizing CalculationInfrastructureBW on HANAMemory SizingSingle NodeRun ABAP report (seenote 1736976)Housekeeping (reducePSA and ChangeLog)HANAEstimate upcomingdata volume (e.g.analyze current ERPtables)Row StoreColumn StoreAdditional CachesCPU SizingDetermine by memorysize and hardwareofferingsNot possible for BW onHANAScale-Out(Total Memory 750 GB)Shared StorageBW on HANA needs atleast 3 nodesAdditional Stand-bynode possibleDisk SizingData Volume(persistence)Log Volume 2013 SAP AG or an SAP affiliate company. All rights reserved.(Total Memory 4 TB*)* Certification pending as of today15

Scalability, Sizing and PerformanceSizing for Growth – ExampleCalculation of system growth over time and the impact on the memory areas (Scale-outscenario)Proactive and seamlessextension of the hardwarecapacityAdd one more nodeAdd a further node 2013 SAP AG or an SAP affiliate company. All rights reserved.16