Welcome to todays training on the data replication scenarios available for SAP HANA.

1
After completing this lesson, you will be able to:
Explain the three replication scenarios for SAP HANA
Describe the key processes for each replication scenario
In-memory reporting and analyzing of business data requires the replication of the data
from a source system to the SAP HANA database. This module provides an overview of
the possible replication methods that are available for the SAP HANA appliance. It also
describes the application fields and lists the main components required for each
method.
The diagram on this slide gives an overview of the alternative methods for data
replication from a source system to the SAP HANA database. Each method handles the
required data replication differently, and consequently each method has different
strengths. It depends on your specific application field and the existing system
landscape as to which of the methods best serves your needs.
3
Trigger-Based Data Replication uses the SAP Landscape Transformation (SLT)
Replication Server to move data from the SAP ERP database or any SAP supported
database into SAP HANA. The replication is done in real-time, so changes done in the
original data source are immediately replicated to HANA. This method of replication
benefits from being database-independent, and can also parallelize database changes
on multiple tables by segmenting large table changes.
Extract-Transform-and Load (ETL) Based Data Replication using SAP BusinessObjects
Data Services can be used to move data from any data source into HANA via
scheduled batches. You can reuse the ERP application logic by reading extractors or
utilizing SAP function modules. In addition, the ETL-based method offers options for the
integration of third-party data providers.
Transaction Log-Based Data Replication using Sybase Replication is based on
capturing table changes from low-level database log files. This method is database-
dependent.
In the next three slides well look more closely at each of these replication methods.
4
The Trigger-Based Replication method uses the SAP Landscape Transformation (SLT)
Replication Server component to pass data from the source system to the SAP HANA
database target system.
The initial load of business data is initiated using the SAP HANA studio. The initial load
message is sent from the SAP HANA system to the SLT system (based on SAP
NetWeaver 7.02 with kernel 7.20 EXT), which in turn passes the initialization message
to the ERP system. The ERP system begins by setting up database transaction log
tables for each table to be replicated. After the transaction tables are completed, the
SLT system begins a multi-threaded replication of data to the target system, which
enables high speed data transfer. The initial load of data can be executed while the
source system is active. The system load that this process causes can be controlled by
adjusting the number of worker threads performing the initial replication.
5
In parallel to the initial load, by means of database-specific triggers, the SLT system
begins detecting any data changes that occur while the initial load process is running.
These changes are logged to the transaction tables, and are propagated to the target
SAP HANA system. The multi-version concurrency control (MVCC) of the SAP HANA
database prevents issues that might be caused by the overlapping of the initial load
process and new database transactions
After the initial load process has completed, the SLT system continues to monitor the
transaction tables in the source system.
6
Extract-Transform-and Load (ETL) based data replication uses SAP BusinessObjects
Data Services to load the relevant business data from the source system and replicate it
to the target SAP HANA database. This method enables you to read the required
business data on the level of the application layer. You deploy this method by defining
data flows in Data Services and scheduling the replication jobs.
Since this method uses batch processing, it also permits data checks, transformations,
synchronizing with additional data providers, and the merging of data streams.
The diagram on this page provides an overview of the ETL-based replication method.
Here, data replication is operated by Data Services. Its main components are the Data
Services Designer, where you model the data flow, and the Data Services J ob Server
for the execution of the replication jobs. An additional repository is used to store the
metadata and the job definitions.
7
As for any replication scenario you have to define a series of parameters for the two
systems involved. Utilizing Data Services you have to set up datastores to define such
parameters. You use the Designer to set up datastores.
Once datastores are set up, Data Services can connect to the source system by RFC.
Based on the metadata imported from the ABAP Data Dictionary to Data Services, you
can determine the business data to be replicated. Data Services offers replication
functions for a variety of data source types. However, for the replication of SAP ERP
data to SAP HANA database, we recommend you use extractors.
Model the data flow for each extractor you have selected: indicate the source for the
data flow, which is the extractor. For the target of the replication, choose a template
table, which is then used in the SAP HANA database to store the replaced data.
Both the initial load of business data from the source system into SAP HANA database,
as well as updating the replicated data (delta handling) is done using SAP
BusinessObjects Data Services. The initial load can be set up by modeling a simple
data flow from source to target. For the update, in most cases, the data flow is
enhanced by a delta handling element, such as Map_CDC_Operation or
Table_ComparisonTransform. It depends on the environment and the requested setup
of the target tables which data flow design best serves your requirements. Although we
recommend you use delta supporting extractors, you can also use SAP ABAP tables.
Since you can schedule the replication jobs when using Data Services, this method is
suitable where the source system must be protected from additional load during the
main business hours. In this way, you can shift the replication workload, for example, to
the night. As a result, the data that is available for reporting always represents the state
reached when the latest replication job was started. Use the Management Console,
which comes with Data Services, to schedule replication jobs. You can choose from
different tools and methods for the scheduling. You can also use the Management
Console to monitor the replication process.
Before the end of this lesson you will be given information on where to access further
training on SAP Data Services.
8
The initial diagram on this page provides an overview of the Transaction Log-Based
Data Replication process using Sybase Replication Agent. This replication method is
only recommended for customers that have been invited to use this technology during
the RTC of the SAP HANA product delivery. If you are not part of this RTC group, SAP
recommends using Trigger-Based Data Replication Using SAP LT (Landscape
Transformation) Replication Server because of the rich feature set offered by this
replication technology.
The main components of this replication method are the Sybase Replication Agent, and
the Sybase Replication Server in SAP HANA.
This more detailed diagram outlines the details of the data replication process and
introduces the additional components of this replication method.
9
The initial load of business data needs to be executed only once to replicate the entire
existing dataset from the source system to the target SAP HANA database. The SAP
HANA Load Controller, a component that resides in SAP HANA, coordinates the entire
replication process: it starts the initial load of source system data to the SAP HANA
database and communicates with the Sybase Replication Server to coordinate the start
of the delta replication.
The initial load can be executed while the source system is active. The Load Controller
initiates the initial load by calling the load component in the source system. This is a
special version of R3load available as a patch from SAP Service Marketplace. The
R3load on the source system exports the data for selected tables in the source system
database and directly transfers this data via sockets to the R3load component in SAP
HANA without any intermediate files. The R3load on the target system imports the data
into the SAP HANA database.
In parallel to the initial load, the Sybase Replication Agent in the source system is
started and detects any data changes that occur while the initial load is already running
to cover every single change. This
detection is performed by reading the logs for committed transactions of the source
system database.
The Replication Agent uses the table metadata from the database to connect the raw
log information with the existing table names. In addition, the Replication Agent
transfers all relevant raw log information
via TCP/IP connection to the Sybase Replication Server on the SAP HANA side. The
Replication Server creates SQL statements from the raw log information received and
sends these statements to the
Sybase Enterprise Connect Data Access (ECDA).
The ECDA connects to the SAP HANA database via Open Database Connectivity
(ODBC) driver and replicates the data changes from the source database by executing
the SQL statements in the SAP
HANA database. The multi-version concurrency control (MVCC) of the SAP HANA
database prevents locks.
The continuous delta replication captures the ongoing data changes in the source
system in real time once the initial load and the simultaneous delta replication have
been completed. All further data changes
are captured and continuously replicated from the source system to SAP HANA using
the same process as the simultaneous delta replication described above.
10
You can learn more about the concepts covered in this lesson by accessing existing
training and other enablement tools and assets on the partner portal. Explore the links
provided on this slide.
Solution Consultant Training:
https://service.sap.com/~form/sapnet?_SHORTKEY=01200252310000087332&_SCEN
ARIO=01100035870000000183&_ADDINC=011000358700001192682007E&
SAP BI Workbook:
http://scn.sap.com/docs/DOC-24342
Product Tutorials:
http://sap.com/LearnBI
SAP Resource Libraries:
https://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000723867&_SCEN
ARIO=01100035870000000183&_ADDINC=&
11
To allow you to familiarize yourself with some of the concepts covered in this training we
have made available a number of offline demonstrations. The scenarios listed on this
slide relate to tasks you would perform in the HANA modellingstudio. Use these
demonstration scenarios to gain a greater understanding of some of the technical
aspects of SAP HANA. You should start with the Modellingscenario and only move on
to the other scenarios when you are ready.
Note that these demonstrations require the iRise Reader to be installed on your system.
You can download the iRise Reader for free from www.irise.com. All that is required for
this download is an email address.
The demonstrations launch in a web browser - expand the view to full screen in the
browser using the f11 key to avoid any issues with small areas being cut off the side of
the demo.
12
Lastly, it is important to note that these demonstrations do not include a great deal of
scripting so you must ensure that you are using the guides to get to know the flow of
the scenario. The clickable areas in the demo have a small black guide icon next to
them. Hover your mouse over the guide to see instructions that will help you proceed
through the scenario. The guide icons are only available when the Guides option in the
iRise reader toolbar is On.
After you have installed the iRise Reader, come back to this page and simply click on
the graphic to access all of the SAP HANA iRise demo content in the Partner Demo
Library.
13
Correct!
Trigger-Based Data Replication uses SAP Landscape Transformation (SLT) Replication
Server can be used to move data from the SAP ERP database or any SAP supported
database into SAP HANA. Extraction-Transformation-Load (ETL) Based Data
Replication uses SAP BusinessObjects Data Services to move data from any data
source into HANA via scheduled batches. Transaction Log-Based Data Replication
Using Sybase Replication is based on capturing table changes from low-level database
log files. This method is database-dependent.
Sorry, that is incorrect. The correct answers are:
Trigger-based Replication
Extraction-transformation Load Replication
Log-based Replication
14
Trigger-Based Data Replication uses SAP Landscape Transformation (SLT) Replication
Server can be used to move data from the SAP ERP database or any SAP supported
database into SAP HANA. Extraction-Transformation-Load (ETL) Based Data
Replication uses SAP BusinessObjects Data Services to move data from any data
source into HANA via scheduled batches. Transaction Log-Based Data Replication
Using Sybase Replication is based on capturing table changes from low-level database
log files. This method is database-dependent.
15
Correct!
Trigger-Based Data Replication uses the SAP Landscape Transformation (SLT)
Replication Server to move data from the SAP ERP database or any SAP supported
database into SAP HANA. The replication is done in real-time, so changes done in the
original data source are immediately replicated to HANA. This method of replication
benefits from being database-independent, and can also parallelize database changes
on multiple tables or by segmenting large table changes.
Sorry, that is incorrect. The correct answer is:
Trigger-based Replication
Trigger-Based Data Replication uses the SAP Landscape Transformation (SLT)
Replication Server to move data from the SAP ERP database or any SAP supported
database into SAP HANA. The replication is done in real-time, so changes done in the
original data source are immediately replicated to HANA. This method of replication
benefits from being database-independent, and can also parallelize database changes
on multiple tables or by segmenting large table changes.
16
You should now be able to:
Explain the three replication scenarios for SAP HANA
Describe the key processes for each replication scenario
For more information on topics discussed in this course, see the references listed here.
Thank you for completing this training.
19