IBM i and SAP HANA

Ron Schmerbauch

rschmerb@us.ibm.com

SAP on IBM i Development

Rochester, MN, USA

Why Power for HANA?

2 © 2015 International Business Machines Corporation

IBM offers HANA on Power for those interested in HANA.

Power as a HW platform for HANA : • Higher thread count

• Higher memory bandwidth

• Faster processors

• More reliable HW components

• Chipkill for memory

• PowerVM

• Virtualization with very little overhead

• Easy to move resources between IBM i and HANA LPARs

• ITG white paper details: For the First Time, Architectural Choice for SAP

Customers That Want to Move to HANA

Possible IBM i & HANA Configurations

4

Application Layer Application Layer

Hardware, Virtualization IBM Power Systems

OS, Database

Application Layer Application Layer

SAP HANA

(read-only copy

of some tables)

2-tier

2-tier

4

2

1. IBM i w/ DB2 only • Best TCO, good performance

• Optimization options as needed

2. IBM i w/ DB2 & HANA Sidecar* (e.g. COPA)

• Subset of data shadowed to HANA

• HANA handles some queries

4. HANA DB for all applications* • IBM i app server and/or legacy apps

• Or use Linux app server

OS

Hardware, Virtualization IBM Power Systems

OS, Database OS

Hardware, Virtualization IBM Power Systems

OS, Database

3-tier

OS

* when available for HoP

3. IBM i w/ DB2 for all except BW • Reliable & performant ERP system on IBM i

• HANA used for BW DB, with i app server

3

Prerequisite: SAP NetWeaver 7.40 SP03 or higher

ERP BW

1 HANA

interface

BW ERP

Application Layer

SAP HANA

(BW DB only) 3-tier

BW ERP

Application Layer

SAP HANA

(all DB Storage)

* when available for HoP

IBM i with HANA Sidecar for selected ERP functions

Goal: Improve performance of selected reporting function(s) in ERP

Best candidate: Large customer, selected transaction available

Considerations:

Can the sidecar solution be used "off the shelf" or is customization necessary?

SAP vision for the future – no sidecar

4

Goal: BW performance improvement

Best candidate: Large customers with extreme BW requirements

Considerations:

DB2 for i EVI's provide columnar benefits and are extended in 4Q2015

BW on HANA infocube data model advantage comes to IBM i in 4Q2015

Performance issues could be results of BW app tuning, not DB

DB migration and more memory...OR...faster storage and/or DB2 SMP

HANA for BW

5

Goal: New S/4 architecture,

"HANA only" applications

Supposed candidate: Large customer

using ERP with SRM, CRM, SCM

Easiest candidates:

Small ERP customer with very little customization

New SAP customer

Most difficult candidate:

Large customer with everything, customized, 24x7.

"Green field" option?

* when available for HoP

Business Suite on HANA

6

Goal: New S/4 architecture,

"HANA only" applications

Best candidate: Large customer

using ERP with SRM, CRM, SCM

with very little customization

Considerations:

SAP release upgrade requirements

"Hanatization" of customized ABAP

3rd party SW – HANA ready?

Data center capacity during transition? Or use the Cloud?

EP, PI, SolMgr, BW(EDW), app servers & other components don't go away

Early adopter costs, risks, unknowns

Business Suite enhancements using CDS on i

* when available for HoP

Business Suite on HANA

7

Goal: Stability and good performance with minimal effort.

Best Candidates: Current customers

Considerations:

Business Suite supported on AnyDB through 2025 (+?)

SAP Core Data Services provides future enhancement options from SAP

• First CDS solutions already shipped on i

SAP chooses when and where to use CDS for AnyDb

NetWeaver 7.5 is the foundation for both S/4 and Business Suite

IBM i only scenario

8

SAP NetWeaver 7.5

"SAP NetWeaver 7.5 is the compatible follow up release of SAP NetWeaver 7.4

and the on-premise foundation for SAP Business Suite (as of Enhancement Package 8 for SAP ERP)

and for the on-premise edition of SAP S/4HANA."

9

Source: http://scn.sap.com/docs/DOC-67382

IBM i Support Roadmap

Arrows indicate general timeframes, not specific dates.

All statements regarding IBM's future direction and intent are subject to change or

withdrawal without notice, and represent goals and objectives only.

In Summary

11

All solutions have attractions and challenges

HANA environment is still evolving and improving

CDS technology is new to everyone

IBM i is running your business today, tomorrow and the next

IBM and SAP are working together

Making HANA on Power a HW alterative

Continuing investment in SAP on IBM i platform

The team will take you through some highlights in our agenda:

NetWeaver 7.5 and CDS

DB2 features for SAP, including EVI Only Access

BW infocube changes and performance results

OS and SAP release Upgrade news

Questions? – Thank You!

Contact: rschmerb@us.ibm.com

See our blog and discuss with us at http://scn.sap.com/community/ibm-i

© 2015 International Business Machines Corporation 12

13 © 2015 International Business Machines Corporation

Source: SAP Teched 2015 Las Vegas TEC206:Architecture and Components of SAP S/4HANA video

14 © 2015 International Business Machines Corporation

Source: SAP Teched 2015 Las Vegas TEC206:Architecture and Components of SAP S/4HANA video

S/4 HANA Migration Scenarios (as of Oct 2015)

15

1. Greenfield/re-implementation

Start from scratch

2. Upgrade and migrate

2-step – may need different weekends

HANAtization of relevant custom code

3. Migrate only

HANAtization of relevant custom code

4. "Suite on HANA" to S/4HANA

Industry Solution restrictions (non-CDS)

5. Split finance from the rest of your ECC DB

Image Source http://public.dhe.ibm.com/common/ssi/ecm/gb/en/gbb14067usen/GBB14067USEN.PDF

OS

Linux Enterprise Server Priority Support for SAP applications

Power - HANA Landscape

SAP HANA®

File System Monitoring

Backup

Sys Mgmt GPFS2, XFS

Server Hardware

POWER7+(non-prod) or POWER8

Standalone or shared/PVM virtualized

Applications

Storage Hardware

Customer choice

High Availability SAP HANA Auto Host-standby & System

Replication, SUSE HA Ext, RH HA Plugin1,

Symantec HA1, Tivoli SA

ECC

BW HA

PowerVM

ECC App

Power Landscape example

CRM

ECC HA

BW

PowerVM

External Storage

ECC, BW, SM App Sbx

ECC QA

BW QA

CRM QA

ECC App

VIO

S

VIO

S

ECC HA QA

HANA

HANA

App

DB/App

DB/App

DB/App

App

HANA

HANA

App

HANA

HANA

App

HANA BW HA QA

BW App

VIO

S

VIO

S

1) Not currently supported with Linux on Power. Contact RedHat for product plans.

2) GPFS is currently supported for Linux on Power by IBM. Contact SAP for plans for certification with HANA on Power..

2 and 3 tier mix

Multiple partitions

VIOS & external storage

Equivalent landscape – on IBM i

DB2 for i®

OS

File System Monitoring

Backup

Sys Mgmt IFS

Server Hardware POWER7+(non-prod) or POWER8

Standalone or shared/PVM virtualized

Applications

Storage Hardware

Customer choice

High Availability Power HA or Logical Replication

ECC, CRM

BW HA

PowerVM

Power Landscape example

ECC HA

BW

PowerVM

External Stoarge

ECC, BW, SM App Sbx

ECC QA, CRM QA

BW QA

VIO

S

VIO

S

i

i

i

i

i

i

VIO

S

VIO

S

i

Simple 2 tier

Fewer partitions

Internal or External Storage

How long can I keep using Business Suite?

Source: http://www.news-sap.com/sap-committed-innovation-choice-sap-business-suite/

"SAP is complementing its innovation commitment by prolonging mainstream

maintenance until end of 2025 for SAP Business Suite 7 core application

releases including the SAP ERP 6.0, SAP Customer Relationship

Management 7.0, SAP Supply Chain Management 7.0 and SAP Supplier

Relationship Management 7.0 applications…."

"SAP will continue to deliver innovations for the on-premise versions of SAP

Business Suite 7 and SAP Business Suite powered by SAP HANA 2013.

SAP Business Suite customers will benefit from state-of-the-art technologies

and business processes… "

What will help SAP deliver innovations for both

Business Suite and S/4HANA for the next 10 years?

Source: Systemkonsolidierungsoptionen für Kunden im Zeitalter von Cloud und HANA

Dr. Carol Gustav / P&I Services: Market Introduction: Product Management & Customer Services, Feb 2015 DSAG TT

19

In Memory Computing: Re-think Paradigms

In-Memory Computing Imperative: Avoid movement of detailed data

Calculate first, then move results

Application

Layer

Database

Layer

Calculation

Calculation

Today Future

20

CDS, not the DB, allows ABAP to shift more work to the DB layer.

Are Core Data Services for HANA only ?

Source: Systemkonsolidierungsoptionen für Kunden im Zeitalter von Cloud und HANA

Dr. Carol Gustav / P&I Services: Market Introduction: Product Management & Customer Services, Feb 2015 DSAG TT

21

Source http://onapsis.com/blog/onapsis-helps-sap-customers-protect-against-10-new-vulnerabilities-affecting-sap-hana

22

" Most of these newly discovered vulnerabilities allow attacks to severely alter

sensitive business data, or to render the systems completely unusable."

"As SAP applications continue to move to a hybrid cloud model the attack

surface is rapidly expanding."

Higher profile makes HANA a target

HANA Delta Store Delta Tables

– Index / Dictionary structure

– Dictionary is not sorted, but in sequence of timely

elements appended

– Thus Updates/Replacements of a vector element are

transformed to insert-only transactions

– Maintained in “delta store” segments

Data representation is maintained not in sorted linear,

but in B+ -Tree-like format

– well suited for fast modifications and merging with main

store data (memory, disk)

– Support range operators

Delta Manager – moves rows to column format

– Asynchronous process which handles version

management of main and delta data

– Background merge of delta data into new

main store column representation

Reorg of column may be necessary for optimal

performance if the data changes

Some tables in HANA are ONLY row based

because they change frequently

Increased memory and CPU

demand during this phase

Source: SAP HANA

Main Store Delta Store

Committed

DB-Updates

HANA’s Persistence – Yes, it needs Disk!

SAP HANA requires on-disk storage for data persistence

– Without disk storage, in-memory data would be lost if HANA stopped or crashed

– On-disk logging is required to maintain data consistency and recoverability

– On-disk backups of the data volumes are required for crash recovery

– Manual log copies are recommended

to prevent data loss from outages

Disk Sizing for HANA:

– DISK(Data) = 4 x RAM(total)

– DISK(logs) = RAM(total)

Data

– SQL Data and undo log information

– Write process is asynchronous

Log

– Information about data changes

– Synchronous write during commit

Legal Information – Please Note

IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion.

Information regarding potential future products is intended to outline our general product direction and it should not be relied on in

making a purchasing decision.

The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material,

code or functionality. Information about potential future products may not be incorporated into any contract. The development, release,

and timing of any future features or functionality described for our products remains at our sole discretion.

Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual

throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the

amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed.

Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

Availability. References in this presentation to IBM products, programs, or services do not imply that they will be available in all

countries in which IBM operates.

The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are

provided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or

advice to any participant. While efforts were made to verify the completeness and accuracy of the information contained in this

presentation, it is provided AS-IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising

out of the use of, or otherwise related to, this presentation or any other materials. Nothing contained in this presentation is intended to,

nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and

conditions of the applicable license agreement governing the use of IBM software.

All customer examples described are presented as illustrations of how those customers have used IBM products and the results they

may have achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these

materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific

sales, revenue growth or other results.

© 2015 International Business Machines Corporation 25

Legal Information – Trademarks, Copyrights Information contained in this material has not been submitted to any formal IBM review and is distributed on “as is” basis without any

warranty either expressed or implied. The use of this information is a customer responsibility.

IBM MAY HAVE PATENTS OR PENDING PATENT APPLICATIONS COVERING SUBJECT MATTER IN THIS DOCUMENT. THE

FURNISHING OF THIS DOCUMENT DOES NOT IMPLY GIVING LICENSE TO THESE PATENTS.

The client examples cited are presented for illustrative purposes only. Actual performance results may vary depending on specific

configurations and operating conditions. It is the user’s responsibility to evaluate and verify the operation of any other products or

programs with IBM products and programs.

IBM, the IBM logo, ibm.com, AIX, BatchPipes, BladeCenter, DB2, DB2 Connect, Netezza, GDPS, GPFS, Netfinity, Intelligent Miner,

OpenPower, Parallel Sysplex, POWER, RACF, Redbooks, RETAIN, System Storage, System p, System x, System z, Tivoli,

WebSphere, zEnterprise, z9, z10, and z/OS are trademarks or registered trademarks of International Business Machines Corp.,

registered in many jurisdictions worldwide. A current list of IBM trademarks is available on the web at “Copyright and trademark

information” at: http://www.ibm.com/legal/us/en/copytrade.shtml

LinkedIn, the LinkedIn logo, the IN logo and InMail are registered trademarks or trademarks of LinkedIn Corporation and its affiliates in

the United States and/or other countries.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems

Incorporated in the United States and/or other countries.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

SAP, R/3, SAP NetWeaver, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned

herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

All other product and service names mentioned are the trademarks of their respective companies.

Data contained in this document serves informational purposes only. National product specifications may vary.

© 2015 International Business Machines Corporation 26