You are on page 1of 44

SAP HANA

LT Replication Server
Overview Presentation
Agenda

• Positioning & Overview

• Architectural Concept

• Core Functions

• Additional Features

• Technical Requirements & Summary

© 2012 SAP AG. All rights reserved. 2


Product Name

SAP Landscape
Transformation
Replication Server
for SAP HANA

© 2012 SAP AG. All rights reserved. 3


SAP HANA 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 Business Objects Data Services


SAP Business Objects 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

Other Data Provisioning Options:


SAP HANA Direct Extractor Connection (DXC) is available as a simple option in ETL (batch)
scenarios for data replication from existing SAP Data Source extractors into SAP HANA
Sybase Event Stream Processor (ESP)*: will be available for replicating real time event streams
from Sybase ESP into SAP HANA

* As part of SAP HANA Roadmap

© 2012 SAP AG. All rights reserved. 4


LT Replication Server Leverages Proven SLO
Technologies

SLO* technologies have been used Application Lifecycle Management


since more than 10 years in hundred
of projects per year
Key offerings foster SAP‘s
Application Lifecycle Management
concept
SAP LT Replication Server leverages
several SLO technologies

*) System Landscape Optimization


© 2012 SAP AG. All rights reserved. 5
Overview

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)

HANA Studio

Application Table Replication Configuration

Trigger Based RFC Replication DB


Delta Recording Connection Engine Connection
Application Table

SAP non-SAP source system SAP LT Replication Server SAP HANA system

Connection(s) between source system and SAP HANA system are Data load and replication are
defined as “Configuration” on the SAP LT Replication Server triggered via SAP HANA Studio

© 2012 SAP AG. All rights reserved. 6


The Set-up of LT Replication Server is Fast and Simple

Installation aspects
• Source system(s): use respective DMIS add-on
• LT Replication Server: use add-on DMIS_2010_1_700 with SP07;
other system requirements (NW 7.02; SAP Kernel 7.20EXT) apply

Configuration steps for SAP LT Replication Server


• Define a schema for each source system
• Define connection to source system
• Define DB connection into SAP HANA
• Define replication frequency (real-time; frequency for scheduled replication)
• Define maximum number of background jobs for data replication

Set-up of data replication in SAP HANA


• Select relevant source system
• Start (initial load only and / or continuous replication)

© 2012 SAP AG. All rights reserved. 7


Commercial Aspects and Software Shipment

Commercial Aspects
SAP LT Replication Server for SAP HANA will be
part of SAP HANA software license model

Software Shipment
SAP LT Replication Server for SAP HANA will be
part of SAP HANA software shipment and fully
integrated into the SAP HANA modeler UI.

© 2012 SAP AG. All rights reserved. 8


SAP HANA Customers using SAP LT Replication Server

Real-time data integration is a key driver for leveraging the power of SAP HANA
in a non-disruptive manner (systems operating seamlessly side-by-side).

Only SAP LT Replication Server allows you to realize these benefits by replicating
data efficiently in real time while protecting your existing investment.

• A majority of “Live SAP HANA” customers use SAP LT Replication Server for data replication
• A lot of prototyping projects are in process many more live customers expected in Q3/2012

SAP LT Replication Server was quickly adopted


and is today the default solution for real-time integration
of SAP and non-SAP sources into SAP HANA

© 2012 SAP AG. All rights reserved. 9


Positioning and Key Benefits of SAP LT Replication Server
for SAP HANA

Key Benefits of the Trigger-Based Approach:


Allows real-time (and scheduled) data replication, replicating only relevant data into HANA
Ability to migrate data into HANA format while replicating data in real-time
„Unlimited“ release coverage (from SAP R/3 4.6C onwards) sourcing data from SAP ERP
(and other ABAP based SAP applications)
Leverages proven SLO technology (Near Zero Downtime, TDMS, SAP LT)
Simple and fast set-up of SAP LT Replication Server (initial installation and configuration in
less than 1day) and fully integrated with HANA Studio

SAP LT Replication Server is the ideal solution for all HANA customers
who need real-time or scheduled data replication sourcing
from SAP and non-SAP sources

© 2012 SAP AG. All rights reserved. 10


Agenda

• Positioning & Overview

• Architectural Concept

• Core Functions

• Additional Features

• Technical Requirements & Summary

© 2012 SAP AG. All rights reserved. 11


LT Replication Concept: Trigger-Based Approach
Architecture and key building blocks

RFC
Read module Structure mapping &
Connection
Transformation

DB
Write module
Connection
Application table Logging table
Application table

DB trigger

SAP LT Replication
SAP source system Server SAP HANA system

Efficient initialization of data Flexible and reliable replication process, Fast data replication via DB connect
replication based on DB trigger incl. data migration LT replication functionality is fully
and delta logging concept (as used for TDMS and SAP LT) integrated with HANA Modeler UI
(as with NearZero downtime approach)

© 2012 SAP AG. All rights reserved. 12


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

DB Read module
Connection

Structure mapping &


Transformation

Application table Logging table


DB
Write module Connection
DB trigger
Application table

Non SAP source SAP LT Replication


system Server SAP HANA system

In a first step, SAP LT Replication Server transfers all metadata table definitions from the non-SAP source
system to the HANA system. From the HANA Studio perspective, non-SAP source replication works as for
SAP sources. When a table replication is started, SAP LT Replication Server creates logging tables within
the source system. As a difference, the read modules are created in the SAP LT Replication Server. The
connection the non-SAP source system is established as a database connection.

© 2012 SAP AG. All rights reserved. 13


Multi System Support 1/2

System A Source systems are


Schema 1 connected to separate
System B
Schema 2 HANA schema on the
same HANA System
Source systems SAP HANA system

Source systems are


System A Schema 1 connected to separate
HANA systems.
System B Schema 1 Schema name can be
Source systems SAP HANA system equal or different

Source systems are


System A connected to same
Schema 1 HANA system and
System B also the same
Source systems SAP HANA system schema

© 2012 SAP AG. All rights reserved. 14


Multi-System Support 2/2
1:N Replication for SAP source systems

SAP source system


is connected to
Schema 1
separate HANA
System A systems or to the same
Schema 2 system with different
SAP Source system SAP HANA systems schema name.

If one source system is connected to


several target schemas (currently up
to 1:4 supported), the relevant target
schema can be selected in the data
provisioning UI.

© 2012 SAP AG. All rights reserved. 15


Agenda

• Positioning & Overview

• Architectural Concept

• Core Functions

• Additional Features

• Technical Requirements & Summary

© 2012 SAP AG. All rights reserved. 16


Configuration and Monitoring Dashboard
Setup of connections in SAP LT Replication Server

Call SAP LT Replication Server


Configuration (Transaction: LTR)

Define configuration data

© 2012 SAP AG. All rights reserved. 17


Configuration and Monitoring Dashboard
Setup for non-SAP source system

Start with transaction LTR

To replicate from Non-SAP source


system select Legacy and the
affected Database System.

Depending on the Database System,


additional required information needs to be
specified (e.g. for DB2 specify the DB
Connection and the tablespace name).

© 2012 SAP AG. All rights reserved. 18


Configuration and Monitoring Dashboard
New Settings for a Configuration

A dedicated tablespace can be


defined for the logging tables. If
more than one tablespace was
already defined, they will still be
displayed.

Flag to allow usage of source


system in different configurations
(1:N replication).
Flag for client-specific load and
replication. The data is only read
from the client which is specified
in the RFC connection.

© 2012 SAP AG. All rights reserved. 19


Configuration and Monitoring Dashboard
Master Job settings

The master job can easily be stopped and


restarted for the relevant configuration

© 2012 SAP AG. All rights reserved. 20


Configuration and Monitoring Dashboard
Statistics

Statistical data can be displayed in the


Statistics tab page. You can view the status,
the latency times, number of records that
have been replicated, and the relevant
operation (insert, update, delete).

© 2012 SAP AG. All rights reserved. 21


SAP HANA Studio
Start Data Replication from SAP HANA System

Choose data provisioning to


launch SAP HANA Modeler UI

1. 1. Select source system as defined in SAP LT


Replication Server; related system information
and schema will be displayed
2. 2. Use button Load and / or Replicate to set up
the data replication
3. 3. Use button Stop Replication to finish
replication
4. 4. Use button Suspend to pause replication
5. 5. Use button Resume to continue replication

© 2012 SAP AG. All rights reserved. 22


SAP HANA Studio – Suspend/Resume

Since SPS03, in the HANA modeler, it is possible to suspend a table


from the replication process and to resume it a later point in time.
Suspend - Pause a table from a running replication
Trigger will not be deleted at the source system
Delta will still be stored in log tables within the source system

Resume - Restart replication for a suspended table


Previous suspended replication will be resumed (no new initial load required)

© 2012 SAP AG. All rights reserved. 23


SAP HANA Studio – Advanced Replication Options

LT replication server offers three additional options, which can be only manually executed
by using an SQL statement on the HANA environment.

Create table
An empty table will be created within the HANA system (for example to start modeling without data
load). Use this option to transfer only the definition of a table into the HANA system. This option
allows you to load data by using another data provisioning tool.

Start delta recording


Only delta recording (including logging table and trigger) will be activated for a specific table.
Allows initial data load with another data provisioning tool or allows replication without an initial
load.

Start delta replication


Data replicated from the source system into HANA system will be started (without initial load).

© 2012 SAP AG. All rights reserved. 24


Agenda

• Positioning & Overview

• Architectural Concept

• Core Functions

• Additional Features
• Table Settings and Transformation Capabilities
• Load from SAP Archives
• Monitoring with SAP Solution Manager
• LT Replication Manager – Mobile Application
• Technical Enabler for Multiple Data Provisioning Use Cases
• SLT and HANA in the Cloud

• Technical Requirements & Summary

© 2012 SAP AG. All rights reserved. 25


Table Settings and Transformation Capabilities 1/4
UI to Specify Table Settings

Transaction IUUC_REPL_CONTENT
2 Select table

1 Select
Configuration

Specific table settings:


Assignment of transformation rules
3
– Reduce Number of Records by Filter
– Conversion of Data
Extension/Reduction of Target Table Structures
Adjust / optimize performance of load and replication

© 2012 SAP AG. All rights reserved. 26


Table settings and Transformation Capabilities 2/4
Selective Data Replication / Filtering

Reduce Number of Records by Filter

RFC/DB DB
Connection Connection

Source system SAP LT Replication Server SAP HANA system

Scenario
Replicating certain data only
Only data of specific years, departments, clients, etc. should be used in HANA

© 2012 SAP AG. All rights reserved. 27


Table settings and Transformation Capabilities 3/4
Transformation Data

Conversion of Data

RFC/DB DB
Connection Connection

Transformation
of Data
Source System LT Replication Server SAP HANA System

Scenarios
To make certain fields anonymous HR reporting
To fill initial fields
To convert units or currency and recalculate amounts and values

© 2012 SAP AG. All rights reserved. 28


Table Settings and Transformation Capabilities 4/4
Structure Change of (Target) Table Structure

Extension/Reduction of Target Table Structures

RFC/DB DB
Connection Connection

Source system SAP LT Replication Server SAP HANA system

Scenarios
Merging the same tables (BSEG) from different systems (and create an additional field, for example a
client field in order to avoid duplicate entries)
Merge different tables into one table in the HANA system
Additional fields are required (for example can be calculated/filled during load/replication)
Not all fields are required in the HANA system

© 2012 SAP AG. All rights reserved. 29


Load from SAP Archive 1/2
Architecture and Key Building Blocks

The ILM API must be available in the source system.


The API can be installed by means of SAP Note
1652039 (46C – 731).

Read Module
RFC
Connection Structure Mapping &
Transformation

DB
ADK Archive Write Module
Connection
Access API
Application Table

ADK Archive
SAP LT Replication
SAP Source system Server SAP HANA system

Archived data can be selected by the date of the archiving session.

© 2012 SAP AG. All rights reserved. 30


Load from SAP Archive 2/2
Define Load Object from SLT System

Select replication configuration


Select Archive Object

Define Selection Criteria

Select Relevant
table within current
archive object

© 2012 SAP AG. All rights reserved. 31


Monitoring with SAP Solution Manager 7.1 SP5

Replication notifications and


alerts are now visible in SAP
Solution Manager 7.1 SP5.

SLT monitoring summarizes the


following information per configuration:
Connectivity to source and target system
Status of latency time last 24h replication
Status of master and load jobs
Trigger status

© 2012 SAP AG. All rights reserved. 32


SAP Replication Manager – Mobile Application 1/2
Benefits and Requirements

Monitor Monitor the data replication process and system parameters.

Execution Trigger execution of important data replication functions.

Higher Flexibility Application can be run anytime and anywhere from a mobile device which is
connected to the internet.

Statistics View Provide an analytical perspective of real-time data replication in terms of latency.

Infrastructure Requirements
• SUP2.1
• Gateway (NW 7.02) (Minimal gateway)
• Backend
• IW_BEP 200 ( SP2.0)
• DMIS_MOB SP01
• DMIS_2010 SP07
• SAP LT Replication Server should be a NW 700 EHP2 with SAP Kernel 7.20 EXT

© 2012 SAP AG. All rights reserved. 33


SAP Replication Manager – Mobile Application 2/2
Screenshots

Statistics
View
Execute

Monitor

Higher
Flexibility

© 2012 SAP AG. All rights reserved. 34


Technical Enabler for Multiple Data Provisioning Use Cases

Table-base Replication integrated into HANA Studio


• Real-time for SAP and non-SAP sources
• Enabling SAP HANA Rapid Deployment Solutions & and SAP HANA
Application Accelerators (e.g. CO-PA)

Replication engine for existing RDS Replication engine for new


Solutions and ERP Accelerators SAP HANA Application Accelerators

CO-PA Accelerator
Reporting in Drill-Down Tool
ERP SAP Banking CRM Sales Accelerated Virtual Info Provider
Operational Financial Pipeline Operative transactions like Top-Down Distribution
Reporting Reporting Analysis FI and CO
• General Ledger
• Profit-Center Accounting
SAP Banking • Asset Accounting
FI/CO
Transaction
Accelerator • Overhead Cost Controlling
History • Material Ledger

© 2012 SAP AG. All rights reserved. 35


SLT and SAP HANA in the Cloud
Architecture and Integration with SLT

IUUC_TAB_ALLOWED

RFC Connection
via WAN

SAP source system

Control table IUUC_TAB_ALLOWED in the SAP source system restricts the set of
tables/clients that are allowed to be defined for load/replication from the HANA Studio
(located in the cloud).

© 2012 SAP AG. All rights reserved. 36


Agenda

• Positioning & Overview

• Architectural Concept

• Core Functions

• Additional Features

• Technical Requirements & Summary

© 2012 SAP AG. All rights reserved. 37


Technical Requirements and System Set-Up Information
for LT Replication Server

RFC DB
Connection Connection
SAP Source system LT Replication Server (*) SAP HANA system

Installation: Installation: Installation:


respective DMIS 2010 version Addon DMIS 2010_1_700 HANA includes LT replication
Minimum support pack level: SP05(**) Minimum support pack level: SP07 functionality fully integrated into the UI of
the HANA modeler

Basic Configuration: Basic Configuration: Basic Configuration:


Optional: define separate table space Define RFC connection to source system Create a DB user (if required)
for logging tables Define DB connection to HANA system
Define RFC user with appropriate Define max. number of jobs to be used for data
authorization replication

System Requirements: System Requirements:


SAP Basis 4.6C and higher SAP Basis: Netweaver 702, with Kernel 7.20EXT
All data bases (64BIT Unicode) PL90 - see SAP note 1597627, =>
currently limited platform availability
Filesystem: 100 GB
RAM: 16-32 GB
CPU: 2-4 cores
Recommended number of background jobs: 10

(*) LT replication server can run on any SAP system with SAP NetWeaver 7.02 ABAP stack (using SAP Kernel 7.20EXT),
for example on Solution Manager 7.1 or the source system – it does not have to be a separate SAP system!

© 2012 SAP AG. All rights reserved. 38


Technical Requirements and System Set-Up Information
for LT Replication Server

DB DB
Connection Connection
Non-SAP Source system LT Replication Server (*) SAP HANA system

Installation: Installation:
Addon DMIS 2010_1_700 HANA includes LT replication
Minimum support pack level: SP07 functionality fully integrated into the UI of
the HANA modeler

Basic Configuration: Basic Configuration: Basic Configuration:


Create DB user for Secondary DB Define DB connection to source system Create a DB user (if required)
connection Define DB connection to HANA system
Define max. number of jobs to be used for data
replication

System Requirements: System Requirements:


the OS/DB restrictions of NetWeaver 7.02 SAP Basis: Netweaver 702, with Kernel 7.20EXT
apply (see at http://service.sap.com/pam) (64BIT Unicode) PL90 - see SAP note 1597627, =>
currently limited platform availability
- Filesystem: 100 GB
- RAM: 16-32 GB
CPU: 2-4 cores
Recommended number of background jobs: 10

(*) LT replication server can run on any SAP system with SAP NetWeaver 7.02 ABAP stack (using SAP Kernel 7.20EXT),
for example on Solution Manager 7.1 or the source system – it does not have to be a separate SAP system!

© 2012 SAP AG. All rights reserved. 39


DB Supportability Matrix (always check the PAR)
Loading Data via SAP LT Replication Server for SAP HANA

Technical availability
Database SAP Sources Non SAP Sources (*)
MSFT SQL Server Enterprise Edition OK OK

Oracle Enterprise Edition OK OK

IBM DB2 LUW/ UDB (DB6) OK OK

IBM DB/2 zSeries OK OK

IBM DB2 iSeries (former AS/400) OK Planned

IBM Informix OK Planned

SAP MaxDB OK OK

Sybase ASE
OK OK
(with DB-Version 15.7.0.11) (with DB-Version 15.7.0.11)

For non-SAP source systems, the customer database license needs to cover a permanent
database connection with 3rd party products like LT replication server.
(*) Since a DB connection from LT replication server to a non-SAP system is required, the OS/DB restrictions of NetWeaver
7.02 apply (see at http://service.sap.com/pam)

© 2012 SAP AG. All rights reserved. 40


SLT and HANA “compatibility matrix” SAP Note 1709225

Source System SLT HANA DB/Studio

DMIS 2010 SP3/4 DMIS 2010 SP4 HANA 1.0 SPS2

DMIS 2010 SP3-7 DMIS 2010 SP5-7 HANA 1.0 SPS3

DMIS 2010 SP3-7 DMIS 2010 SP5-7 HANA 1.0 SPS4

• SAP HANA can be upgrade from SPS3 to SPS4 without upgrading DMIS component
• The DMIS component can be upgraded from SP5 to a higher support package level without
the need to upgrade the HANA database or studio

If not all systems are based on the latest support package,


some functionalities like 1:N replication or
Load from SAP Archives might not be available.

© 2012 SAP AG. All rights reserved. 41


Positioning and Key Benefits of SAP LT Replication Server
for SAP HANA

Key Benefits of the Trigger-Based Approach:


Allows real-time (and scheduled) data replication, replicating only relevant data into HANA
Ability to migrate data into HANA format while replicating data in real-time
„Unlimited“ release coverage (from SAP R/3 4.6C onwards) sourcing data from SAP ERP
(and other ABAP based SAP applications)
Leverages proven SLO technology (Near Zero Downtime, TDMS, SAP LT)
Simple and fast set-up of SAP LT Replication Server (initial installation and configuration in
less than 1day) and fully integrated with HANA Studio

SAP LT Replication Server is the ideal solution for all HANA customers
who need real-time or scheduled data replication sourcing
from SAP and NON-SAP sources

© 2012 SAP AG. All rights reserved. 42


Key Information Sources and Contacts

General SAP Note - LT Replication Server for HANA:


SAP Note 1605140: includes all important information, links to overview presentation,
offline demo as well as SAP corrections

Service Market Place and Help Portal


(http://service.sap.com/hana; http://help.sap.com/hana)
Installation Guide
Security Guide
Operations Guide

Do not hesitate to contact your SAP Account Team or the HANA Customer
Solution Adoption Team for more details.

© 2012 SAP AG. All rights reserved. 43


© 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects
purpose without the express permission of SAP AG. The information contained Explorer, StreamWork, and other SAP products and services mentioned herein as
herein may be changed without prior notice. well as their respective logos are trademarks or registered trademarks of SAP AG
in Germany and other countries.
Some software products marketed by SAP AG and its distributors contain
proprietary software components of other software vendors. Business Objects and the Business Objects logo, BusinessObjects, Crystal
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business
Microsoft Corporation. Objects products and services mentioned herein as well as their respective logos
are trademarks or registered trademarks of Business Objects Software Ltd.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, Business Objects is an
System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, SAP company.
zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390
Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other
POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, Sybase products and services mentioned herein as well as their respective logos
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP
Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, company.
Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM
All other product and service names mentioned are the trademarks of their
Corporation.
respective companies. Data contained in this document serves informational
Linux is the registered trademark of Linus Torvalds in the U.S. and other purposes only. National product specifications may vary.
countries.
The information in this document is proprietary to SAP. No part of this document
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or may be reproduced, copied, or transmitted in any form or for any purpose without
registered trademarks of Adobe Systems Incorporated in the United States and/or the express prior written permission of SAP AG.
other countries.
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.
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.

© 2012 SAP AG. All rights reserved. 44