EIM106

Prasad Illapani, Product Management & Strategy (SAP HANA) SAP Labs LLC, Bellevue, WA

Joerg Hoffmeister, Product Management & Strategy (SAP HANA) SAP AG, Berlin, Germany

EIM106

SAP HANA – Data Provisioning for Replication with SAP and Non-SAP Applications

© 2012 SAP AG. All rights reserved. 2

Disclaimer

This presentation outlines our general product direction and should not be relied on in making a

purchase decision. This presentation is not subject to your license agreement or any other agreement

with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to

develop or release any functionality mentioned in this presentation. This presentation and SAP's

strategy and possible future developments are subject to change and may be changed by SAP at any

time for any reason without notice. This document is provided without a warranty of any kind, either

express or implied, including but not limited to, the implied warranties of merchantability, fitness for a

particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this

document, except if such damages were caused by SAP intentionally or grossly negligent.


Agenda

SAP HANA Data Provisioning - Positioning

SAP HANA Data Provisioning - Options

SAP LT Replication Server (SLT)

SAP Data Services (DS)

SAP Direct Extractor Connection (DXC)

SAP HANA Data Provisioning – What’s new in SAP HANA SPS05?

Demos – Loading data into SAP HANA


SAP HANA SPS04: Data Provisioning Positioning

SAP LT Replication Server SAP LT Replication Server (SLT) is positioned for real-time data replication from SAP and non-SAP sources

(SAP supported data bases only)

-> Mainly recommended for real time data replication business scenarios

SAP Data Services SAP Data Services (DS) is positioned for batch load-based data replication from non-SAP sources and SAP

sources (with complex ETL requirements)

-> Mainly recommended for batch type data replication business scenarios

SAP HANA Direct Extractor Connection (DXC) DXC is available as a simple option in batch mode for data replication from existing SAP Data Source extractors

(ERP) into SAP HANA.

-> Mainly recommended for batch type data replication for stand alone HANA business scenarios

Other Data Provisioning Options Sybase Event Stream Processor (ESP) * : will be available for replicating real time Event Streams from Sybase

ESP (CEP) into SAP HANA

* Will be available as part of SAP HANA SPS05 and Sybase ESP 5.1-SP1


Data Provisioning with SAP HANA 1.0

SAP In-Memory Computing Studio

SAP In-Memory Database

Calculation and

Planning Engine Row & Column

Storage

* Sybase ESP 5.1-SP1, Q4-2012

SAP LT

Replication Server

SAP Business

Suite

SAP BW

Non-SAP Data Sources

Activation

Queue

In memory DSO

SAP Data

Services

Sybase Replication

Server

SAP HANA Direct

Extractor

Connection**

Sybase Event Stream

Processor *

Trigger Based,

Real Time

ETL, Batch

Extractor

Batch

XS Engine

Log Based,

Real Time

Trading & Order

Management Systems ODBC

SAP HANA

Http/Https

DB Connection

ODBC

** SAP ERP & BW Extractors

Event Streams

Real Time

Data Sources

SAP BusinessObjects

tools Other query tools

SQL BICS SQL MDX

ECDA/ODBC


SAP HANA system SAP source system

SAP HANA Data Provisioning Options:

1. SAP LT Replication Server

SAP LT Replication Server

Application Table

Trigger Based

Delta Recording Replication Engine

Application Table

RFC

Connection

HANA Studio

DB

Connection

Replication Configuration

Connection(s) between source system and SAP HANA system are

defined as “Configuration” on the SAP LT Replication Server

Data load and replication are

triggered via SAP HANA Studio

SAP LT Replication Server does not have to be a

separate SAP system and can run on any SAP system

with SAP NetWeaver 7.02 ABAP stack (Kernel 7.20EXT)


SAP HANA system SAP LT Replication Server SAP source system

LT Replication Concept: Trigger-Based Approach Architecture and key

building blocks

Efficient initialization of data

replication based on DB trigger

and delta logging concept

(as with near zero-downtime approach)

Flexible and reliable replication process, incl.

data migration

(as used for TDMS and SAP LT)

Fast data replication via DB connection

LT replication functionality is fully

integrated with HANA Modeler UI

Application table Logging table

DB trigger

Read module Structure mapping &

Transformation

Application table

Write module

RFC

Connection

DB

Connection


SAP HANA system SAP LT Replication Server Non SAP source system

LT Replication Concept: Trigger-Based Approach Replication from non-SAP sources

SAP LT replication server transfers in a first step all metadata table definitions from the non-SAP source system to the SAP HANA system into

the tables DD02L and DD02T.

Note: For non-SAP source systems, the customer database license needs to cover a permanent database connection with 3rd party products

like LT replication server.

Application table Logging table

DB trigger

Read module

Structure mapping &

Transformation

Application table

Write module

DB

Connection

DB

Connection



2. SAP Data Services 4.1

SAP HANA Appliance

SAP HANA DB

In-Memory

SAP

Data Services 4.1

SA

P H

AN

A S

tud

io

High Performance

Highly-scalable engine to move large

volumes of data into HANA

Integrated with HANA‟s bulk-load interfaces

Wide Connectivity

Data and Metadata connectivity to all major

enterprise data sources

Native, fast connectivity to Applications,

RDBMS, Files, Text

Powerful Transformations

Built-in transformations for data quality (*)

Support for non-relational data formats

including text and XML

SAP

Business Suite

SAP BW

Structured/Text Data

Sources

*1

(*) = Requires additional licenses *1 = SAP HANA Studio works with DS to

access external metadata


NEW in SAP Data Services 4.1*

Data Services Workbench for data loading into SAP HANA

First release with a new, Eclipse-based user interface design for Data Services.

Addressed Scenario: Replicate data and metadata (table definitions) from 3rd party databases into SAP HANA

via a simple wizard.

In 3 easy simple steps, you can replicate millions of records and hundreds of tables from any source to your

SAP HANA target :

Set up connections to source and target system

Select the required tables from the source (or simply select all tables)

Generate and execute the job to move all data with one mouse click

Once the wizard exits, more additional features can be added: filters, complex data mappings

(expressions and functions), load options, delta loading strategy, etc.

*SAP Data Services 4.1 - RTC in June 2012


SAP Data Services 4.1 – Workbench Design Replication job

HANA (8 selected tables) Step 1: Select source

and target connections

(database or SAP

application).

Step 2: Select tables

for replication, target

tables will be

generated

automatically.

Step 3: Deploy your

Data Services job and

execute.


SAP Data Services 4.1 – Workbench Monitor job run

Built-in capabilities to monitor the data loading

See load progress in real-time

Compare historic load times



3. SAP HANA Direct Extractor Connection (DXC)

Provides Semantically Rich Data from SAP Business Suite to

SAP HANA

Ensures data appropriately represents the state of business

documents from ERP

Application logic to “make sense of the data” already built into many

extractors

Simplicity / Low TCO

Re-uses existing proprietary Extraction, Transformation, and Load

mechanism built into SAP Business Suite systems, over a simple

http(s) connection to SAP HANA

No additional server or application needed in system landscape

Change Data Capture (delta handling)

Efficient data acquisition – only bring new or changed data into SAP

HANA

DXC provides a mechanism to properly handle data from all delta

processing types

Leverage pre-existing foundational data models of SAP Business Suite entities for use in SAP HANA data mart scenarios

Significantly reduces complexity of data modeling tasks in SAP HANA

Speeds up timelines for SAP HANA implementation projects

SAP ERP

Extractor

DataSource (flat structure)

ERP data

Embedded BW

DataSource

PSA

generic data transfer

InfoCubes

Data Store Objects

InfoObjects generic data transfer

SAP HANA

Activation

Queue

Active

version

In memory DSO

Status

Activation

Processing


SAP HANA Direct Extractor Connection: Details - 1 -

SAP HANA Direct Extractor Connection (DXC)

utilizes the DataSource extractors that exist in SAP Business Suite systems

Originally developed for use with BW

DXC is for use in SAP HANA standalone (data mart) scenarios. BW on SAP HANA is a separate topic.

DXC utilizes the embedded BW

To enable extraction, which exists inside all NetWeaver 7.0 or higher ABAP-based systems

With NetWeaver 7.0, BW is automatically included inside NetWeaver ABAP

This is true for ERP systems e.g. ECC 6.0 and higher

– also others, e.g. CRM 7.0 and higher, etc.

In typical SAP Business Suite systems, the embedded BW is not utilized

– customers typically have separate BW systems

DXC uses the embedded BW system to enable extraction and monitoring only

– Data flow is redirected –> it gets sent to SAP HANA

– Note: Modeling in the embedded BW is not part of the DXC solution

Note: An architectural variation is available, which uses a “sidecar” BW instead of the embedded one.



DXC is available for SAP Business Suite systems based on NetWeaver 7.0 or higher, such as

ECC 6.0 or higher

Most customers already have the Support Package level needed on source SAP Business Suite system, e.g. SAP NW 7.0

Support Package Stack 19 – first available Nov 2008

DXC only requires applying a special SAP note

The extraction from the SAP Business Suite system -> controlled from the Data Warehousing

workbench inside the embedded BW

When data is extracted from, the SAP Business Suite system, it is not loaded into the PSA of the embedded BW -

it is redirected instead and sent to SAP HANA

– it gets loaded into in-memory DSO‟s activation queue

– and then gets activated into the active table of the in-memory

However, in the data load monitor of the embedded BW, the data load into the activation queue in the DSO in SAP HANA

appears like data is loading into the PSA in the embedded BW



Delta processing (aka “change data capture”)

Works the same for DXC as it would if BW is the receiving system

– If the DataSource is delta enabled, then delta-data is available with SAP HANA Direct Extractor Connection

DXC internally in HANA uses

The ICM (Internet Connectivity Manager) receives XML packages over the http(s) connection

A mechanism written on the XS Engine (special runtime component for SAP HANA)

– receives data packages from ICM, converts format

– inserts the records into the activation queue of the in-memory DSO

– activation processing -> records go into the active table in proper sequence

Both the ICM and XS Engine components must be enabled in SAP HANA to utilize DXC


SAP HANA Data Provisioning: What’s new in SAP HANA SPS05*

Data Provisioning Workbench

A new „Data Provisioning Workbench‟ editor inside SAP

HANA studio with a common Unified Model.

Leverage SAP HANA Repository for authoring runtime

metadata storage objects.

New Data Provisioning runtime plugins at the server level

to handle source connectivity and other metadata

services.

Open unified Architecture with Administration, Monitoring

API Services for all Data Provisioning Components (SLT,

DXC).

A common UI end to end experience to the users for all

types of replication scenarios via SAP HANA studio.

* SAP HANA SPS05, RTC Q4 2012

Note: This is the current state of planning and it may be

changed by SAP at any time



Sybase ESP-5.1 Integration with SAP HANA 1.0

?

INPUT

STREAMS

Sensor data

Transactions

Events

Application

Studio

(Authoring)

ODBC**

SAP Sybase Event

Stream Processor

ESP-5.1

Database

Dashboard

Message

Bus

SAP HANA 1.0

SAP HANA

Studio

SAP HANA

Database

High speed smart capture: SAP Sybase ESP can apply logic

to transform, filter, aggregate, enrich incoming event streams

and capture data in SAP HANA

SAP Sybase ESP can query SAP HANA database to provide

context for processing incoming events


** Sybase ESP 5.1 SP1- ODBC Adapter, RTC Q4 2012

Note: This is the current state of planning and it may be changed by SAP at any time



SAP LT Replication Server

Technical readiness for replication of SAP Business Suite on SAP HANA

SLT for SAP BW: ready for proof-of-concepts and prototyping projects

Integrated use of SLT by ERP and other SAP HANA Application

Accelerators

Improved usability

– Help Center with detailed context-related documentation

– Advanced status tracking (when using Access Plan / Range

Calculation)

Improved stability

– Eliminate manual steps on SLT system after implementing a note or

support package

– Support related expert functions streamlined

New and improved performance options

– Data load using ROW ID approach with reading type 4

Optimized job management: free-up background jobs and resources for

tables with low change rates


Note: This is the current state of planning and

it may be changed by SAP at any time

Demo Loading data into SAP HANA


Further Information

SAP Public Web

http://help.sap.com/hana

http://scn.sap.com/community/data-services

https://www.experiencesaphana.com/Cached

SAP Education and Certification Opportunities

www.sap.com/education

Watch SAP TechEd Online

www.sapteched.com/online

http://scn.sap.com/welcome

https://portal.wdf.sap.corp/go/crm-rollout-map





http://www.sap.com/education

http://www.sapteched.com/online

Feedback Please complete your session evaluation for

EIM106

Thanks for attending this SAP TechEd session.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express

permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of

other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of

Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System

z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7,

POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize,

XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere,

Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

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

Systems Incorporated in the United States and other countries.

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

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

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or

registered trademarks of Citrix Systems Inc.

HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web

Consortium, Massachusetts Institute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri,

and Xcode are trademarks or registered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry

Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered

trademarks of Research in Motion Limited.

© 2012 SAP AG. All rights reserved.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads,

Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice,

Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork,

SAP HANA, 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.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web

Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects

is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services

mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc.

Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG

in Germany and other countries. Crossgate is an SAP company.

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.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied,

or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

EIM106

Documents

Transcript of EIM106