SAP HANA 2.0 For SAP Business One - Smbsummit2019

Transcription

SMB Innovation Summit 2019Internal SAP Employees and Partners OnlySAP HANA 2.0 for SAP Business One(Focus: Multitenant Database Containers)Satish Kumar Movva & Challen Song, SAP B1 LPEMarch 13, 2019

Legal disclaimerThe information in this presentation is confidential and proprietary to SAP and may not be disclosed without thepermission of SAP. This presentation is not subject to your license agreement or any other service or subscriptionagreement with SAP. SAP has no obligation to pursue any course of business outlined in this document or any relatedpresentation, or to develop or release any functionality mentioned therein. This document, or any related presentationand SAP's strategy and possible future developments, products and or platforms directions and functionality are allsubject to change and may be changed by SAP at any time for any reason without notice. The information in thisdocument is not a commitment, promise or legal obligation to deliver any material, code or functionality. This documentis provided without a warranty of any kind, either express or implied, including but not limited to, the implied warrantiesof merchantability, fitness for a particular purpose, or non-infringement. This document is for informational purposesand may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this document,except if such damages were caused by SAP s willful misconduct or gross negligence.All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differmaterially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements,which speak only as of their dates, and they should not be relied upon in making purchasing decisions. 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Confidential: Released for Partners2

AgendaIntroduction to SAP HANA 2.0 Key InnovationsSAP HANA 1.0, 2.0 Release and Maintenance StrategyUpgrading to HANA 2.0 and Hardware RequirementsDeep Dive into HANA Multitenant Database Containers (MDC) FeatureB1 10.0 plans to support HANA Multitenant Database Containers (MDC)Where to find more informationCall to action 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Confidential: Released for Partners3

Introduction toSAP HANA 2.0 Key Innovations

SAP HANA: The only business data platform for the intelligent enterpriseSimplify, accelerate, innovateSAP HANA PLATFORMAPPLICATION DEVELOPMENTWeb ServerFiori UXJavaScriptGraphicModelerApplication LifecycleManagementADVANCED ANALYTICAL sStreamingAnalyticsSeriesDataBusinessFunctionsDATA INTEGRATION & QUALITYData VirtualizationELT & ReplicationDataQualityHadoop &Spark IntegrationRemoteData SyncOpennessAdmin &SecurityHigh Availability &Disaster RecoveryDATABASE MANAGEMENTColumnarOLTP OLAPMulti-Core &ParallelizationAdvancedCompression 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Confidential: Released for 5

SAP HANA 2.0Key Innovations (1)Analytical IntelligenceTransformedDatabase ManagementTransformedFree IT to Focus on Innovation SAP HANA CockpitImprove admin and monitoring of multipleDBs & tenantsDiscover Insights to Drive Innovation New PAL algorithmsDiscover patterns with machine learning Text AnalysisIntegrate text analysis into applicationsusing SQL & Web IDE for SAP HANA;Sentiment analysis for JapaneseWorkload ManagementManage system overheadActive/Active Read-EnabledLoad balance read-intensive workloadsHigh availabilityMulti target replicationApplication DevelopmentTransformed Develop Solutions that Power Innovation Extended application server (XSA)Increase efficiency with BYO language& runtime; Python runtime, Javaupdate to Tomcat 8.x, Node.js 8.x Tooling Client InterfacesNew XSA admin cockpit, generaltooling and usability enhancementsExternal Machine Learning integrationfor SAP HANACall Google TensorFlow model throughSQLScript[1] Only few of the HANA 2.0 key innovations are listed here, some of the features will require additional licenses to be purchased or not supported in your current licensing model. 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL6

SAP HANA 1.0 and SAP HANA 2.0Release and Maintenance Strategy

SAP HANA Release StrategyCustomers feedbackTodaySAPHANASPS 12SAPHANA 2.0NewEnd of Maintenance: May 2019Releases: 2 SPS per yearMaintenance duration of SPS: 1 yearEnd of Maintenance: May 2021Releases:1 SPS per yearMaintenance duration of SPS: 2 years startingwith SPS 02Last SPS of SAP HANA 2 will have 5 year longterm maintenanceSAP HANA Revision Strategy slide deck available from https://service.sap.com/ sapidb/011000358700001182742013 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL8

SAP HANA Maintenance StrategyRevision Strategy for SAP HANA 1.0 SPS12 SAP will provide Maintenance Revisions for SAP HANA 1.0 SPS12 for a period of 5 years after RTC Maintenance Revisions for SAP HANA SPS12 are not scheduled, they are delivered on demandSPS 12SPS 12RTCDSP (1)SPS 12 Maintenance Revisions SPS 11SPS 11RTCDSP(1)Dec2015March2016[1] (D)atacenter (S)ervice (P)oint, see note SAP Note 2021789 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNALJune2016Sept2016May2021See SAP Note 2021789, 2378962 for further details9

SAP HANA Maintenance StrategyRevision Strategy for SAP HANA 2.0 New capabilities are introduced once a year, every time a new SAP HANA Support Package Stack (SPS) isreleased. This happens normally beginning of April. SAP is providing bug fixes and security patches for every SPS for 2 years after RTC* The last SPS of a major product version is in maintenance for 5 years after RTC We recommend that maintenance timelines and project go live dates are adjusted to this release scheduleSPS 04SPS 03SPS 02RTCRTCRTCSPS 01RTCSPS il2020*except for SPS 00 and SPS01See SAP Note 2021789, 2378962 for further details 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL10

Upgrading to HANA 2.0 andHardware Requirements

SAP HANA Maintenance StrategyUpgrade to SAP HANA 2.0– SAP HANA 2.0 is upward compatible, customers just have to do a normal upgrade, no migration– Upgrade from any SAP HANA system running on SPS10 or newer is possible Customers on SAP HANA SPS09 or lower first need to upgrade to a HANA SPS SPS 10* However we recommend to first upgrade to the latest SPS12 revision before upgrading to SAP HANA 2.0 to be able touse Capture & Replay tool for regression testsSPS 10SPS 11SPS 12RTCRTCRTCHANA 2.0SPS 00HANA 2.0SPS 01RTCRTCSPS 12 Maintenance RevisionsMay2021*For details on possible update paths, see note 1948334; Upgrading a HANA 1 system to HANA 2 2372809 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL12

Upgrading to SAP HANA 2.0Hardware requirements, strongly recommended.Hardware Requirements for SAP HANA 2.0 on Intel-Based HardwarePlatforms at least Intel Haswell CPU or later are strongly recommended. Specifically, if you are running an upgrade of a productive HANA systemfrom SAP HANA 1.0 to SAP HANA 2.0 you can use Intel Ivy Bridge orWestmere CPU based compute nodes.For example: Dell R620/ T620 / R920 are based on Intel Ivy Bridge processor andcertified for B1H at that time. Dell R630/ T630 / R730/ R930 are based on Intel Haswell processor andcertified for B1H at that time. The Intel Haswell processor were laterreplaced by Intel Broadwell processors for Dell R630/ T630 / R730/ R930. Now, Dell R640/ R740 are based on Intel Skylake processors.For details on mandatory and options upgrade steps, see note 2469025, 2372809; Hardware requirements for HANA 2.0, see note 2399995 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL13

Deep DiveHANA Multitenant Database Containers (MDC) Feature

SAP Multi-Tenancy OptionsHorizontal ViewMultiple Components,one Database (MCOD)Multiple Components / Instances,one System (MCOS, Virtualization)Multitenant Database Containers,one HANA Instance (MDC)App XApp YApp XApp YApp XApp YSchema XSchema YSchema XSchema YSchema XSchema YDatabaseDatabaseTenant DBTenant DBSAP HANA InstanceSAP HANA InstanceOSOSDatabaseSAP HANA InstanceSAP HANA InstanceOSHypervisor (just for Virtualization)OSHWHWHWSee SAP Note 1788665See SAP Note 2096000See Notes 1661202 1826100 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Confidential: Released for Partners15

SAP HANA hardware deployment optionThird-party HANA virtualization and native HANA multitenancy Virtualization and multitenancy are complementary offerings. Not competitive technologies.App XApp YSchema XSchema YDatabaseDatabaseSAP HANA InstanceSAP HANA InstanceOSOSApp XApp YSchema XSchema YTenant DBTenant DBSAP HANA InstanceHypervisorOSHWHWSAP HANA VirtualizationSAP HANA MultitenancyThird-party virtualization/partitioningtechnologies are leveraged to host multipleisolated SAP HANA instancesEvery database tenant represents a dedicatedshare of an SAP HANA instance data,configuration, user management, and properties 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Confidential: Released for Partners16

SAP HANA Multitenant Database ContainersNew administration layer containing a System database Landscape topology information System-wide parameter settings Focal point for complete backup of all databases Resource management for all tenant DBs (CPU, memory, etc)0 to n tenant databasesIndividual backup/restore of tenant databaseOne database software version for a SAP HANA system (alltenant databases and system database)AppConnect to:NDB.DB AAppConnect to:NDB. port SAP HANASID: NDBNDB.SystemDBNDB.DB ANDB.DB BHA/DR setting covers whole SAP HANA system: all tenantsare included in a HA/DR scenario 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Confidential: Released for Partners17

B1 10.0 plans to supportHANA Multitenant Database Containers (MDC)

Wave 1: adopt HANA 2.0 with full MDC supportHANA 1.0 with singlecontainer modeHANA 2.0 with Multitenant Database Containers (MDC)SUSUSUCompany1Company2Company xKey info: Full MDC y2Company2Company xCompany ySBOCOMMONSBOCOMMONCOMMCOMMTenant DB ATenant DB B Connect string (ODBC/JDBC) requestaddition parameter for MDC Using name of DB container(Recommend) Using SQL port (compatible) Extracted/embedded SLD datasupport (Option)SLD Production QA/ TestSBOCOMMON SU A SU B Install/ upgrade wizard enhancement 10.0 PL x 10.0 PL y HANA High available supportCOMMSLDDatabaseLicenseSLD (Option)System DBSAP HANA InstanceSAP HANA InstanceOSOSHWHW 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Confidential: Released for Partners19

ODBC connection string For Single-Database:DRIVER {HDBODBC};UID myUser;PWD myPassword;SERVERNODE myServer:30015;DATABASE Schema Name For Multi-Database: (new DATABASENAME parameter)DRIVER {HDBODBC};UID myUser;PWD myPassword;SERVERNODE myServer:30013;DATABASENAME TENANTDB A;DATABASE Schema Name 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Confidential: Released for Partners20

New Installation & Upgrade to HANA2.0Upgrade:Ports and URLs will be not changed after theupgrade.1st TenantNDBSQL Port30015New Installation:Tenant DB Port:SystemDBSQL Port30013SID: NDBSID: NDB3 instance number 153 instance number 40 3 instance number 99SystemDB with port:Upgrade from HANA1.0 to HANA 2.0 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Confidential: Released for Partners3 instance number 1321

SAP Business One, version for SAP HANAPlanned support for HANA Multitenant Database Containers (MDC) Starting SAP HANA 1.0 SPS 09 (Revision 90), MDC supported Starting with HANA 2.0 SPS 01 (Rev 10), MDC is the onlyoperational mode. Single container system can be migrated to a tenant databasesystem. Upgrading single container system from any lower version toHANA 2.0 SPS 01, the system will automatically be converted tomultitenant system. B1H will support MDC from HANA 2.0. Do not allow install/ convertto MDC in HANA 1.0. 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Confidential: Released for Partners22

Sizing of multitenant database containersPerform a sizing exercise for each application or usecase, and then utilize an additive sizing approach.Additive sizing: Perform a sizing estimation for eachtenant database, utilizing known sizing approaches as if itwere a single database.Next, add the individual sizing estimates together andavoid underestimating.Number of tenant databases that can be deployed is limited by available resources:Architecturally, each tenant database has its own index server, and upon initial deployment, consumes approximately 8 GB (before anyapplication data is added).This means that the actual number of tenant databases that can be deployed is limited by available resources; in other words, a largenumber of very small tenant databases is not possible given the current tenant databases architecture. 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Confidential: Released for PartnersSee SAP Note 2096000 for further details23

Demo

Multiple containers: the only operational mode

HANA studio - add system: Single container

HANA studio - add system: Multiple containers

More information What’s New in HANA 2.0 from SAP PartnerEdge Portal Top Assets for Sales for SAP HANA 2.0 from SAP PartnerEdge Portal SAP HANA Academy – SAP HANA 2.0 Playlist on YouTube 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Confidential: Released for Partners29

Next ies tobenefit from HANA2.0 innovationsB1H Deals withconfidenceFrom HANA 2.0documentation 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Confidential: Released for Partners30

Meet us at the expert table 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Confidential: Released for Partners31

Thank you.Contact information:Satish Kumar Movva & Challen SongAPJ SAP LPEsatish.kumar.movva@sap.com & challen song@sap.comGamification Challenge CodeBAN3o4rBy entering this SAP Breakout Sessioncode you will be granted 10 points55

Appendix

ReferencesRelease and Maintenance Strategy SAP Release Strategy Brochure https://service.sap.com/releasestrategy SAP HANA 1.0 Revision and Maintenance Strategy, SAP Note 2021789 SAP HANA 2.0 Revision and Maintenance Strategy, SAP Note 2378962Update/ Upgrade Path and How-To SAP HANA Supported Operating Systems, SAP Note 2235581 Hardware requirement for SAP HANA 2.0, SAP Note 2399995 Recommended update paths for SAP HANA Maintenance Revisions, SAP Note 1948334 How-To: Upgrading to SAP HANA 2.0, SAP Note 2469025 Mandatory Preparation Steps for Upgrading a SAP HANA 1 to SAP HANA 2 System, SAP Note 2372809SAP HANA Multitenant Database Containers (MDC) Multitenant database containers will become the standard and only operation mode, SAP Note 2423367 FAQ: SAP HANA Multitenant Database Containers (MDC), SAP Note 2101244 SAP HANA tenant databases - Additional Information, SAP Note 2096000More InfoWhat's New in the SAP HANA Platform 2.0 SPS 03SAP HANA 2.0 SPS 03 Administration GuideSAP HANA 2.0 SPS 03 Tenant Databases Operations GuideSAP HANA Administration with SAP HANA Cockpit 2.0 SP 09What’s New in the SAP HANA Cockpit 2.0 – by the SAP HANA Academy 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Confidential: Released for Partners34

SAP HANA Maintenance Strategy Upgrade to SAP HANA 2.0 - SAP HANA 2.0 is upward compatible, customers just have to do a normal upgrade, no migration - Upgrade from any SAP HANA system running on SPS10 or newer is possible Customers on SAP HANA SPS09 or lower first need to upgrade to a HANA SPS SPS 10*