«SAP Landscape Transformation Replication Server Document Version: 3.1 – 2016-05-11 SAP Landscape Transformation Replication Server For SAP HANA ...»
Application Operations Guide CUSTOMER
SAP Landscape Transformation Replication Server
Document Version: 3.1 – 2016-05-11
SAP Landscape Transformation Replication Server
For SAP HANA Platform SPS12
Type Style Description
Example Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
Example Emphasized words or expressions.
Technical names of system objects. These include report names, program names,
EXAMPLEtransaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.
Output on the screen. This includes file and directory names and their paths, messages, Example names of variables and parameters, source text, and names of installation, upgrade and database tools.
Exact user entry. These are words or characters that you enter in the system exactly as they Example appear in the documentation.
Variable user entry. Angle brackets indicate that you replace these words and characters Example with appropriate entries to make entries in the system.
Keys on the keyboard, for example, F 2 or E N T E R.
The current version of the Application Operations Guide is at service.sap.com/instguides on SAP Service Marketplace.
Version Date Change 1.9 2013-08-08 Revised published version for SAP HANA Platform SPS06 and DMIS 2011 SP05 2.0 2013-11-18 Revised published version for SAP HANA Platform SPS07 and DMIS 2011 SP05 2.1 2014-01-29 Revised published version for SAP HANA Platform SPS07 and DMIS 2011 SP06 2.1.1 2014-03-06 Updates to reflect application component chan
1 Getting Started
1.1 About this Guide
1.2 Global Definitions
1.3 Important SAP Notes
1.4 SAP Landscape Transformation Replication Server Guides
1.5 Key Terms
2 Basic Concepts and System Landscape Options
2.1 Basic Concepts of Trigger-based data Replication using SAP LT Replication Server for SAP HANA
2.2 System Landscape and Installation Options
3 Configuration Information and Replication Concepts
3.1 Technical Prerequisites and Authorization Aspects
3.1.1 Software Installation
3.1.2 System Connections and Authorizations
3.1.3 Creating a Configuration
3.1.4 Additional Information for Non- ABAP Source Systems
3.2 Managing the Replication Process Using the SAP HANA Studio
3.3 Accessing the Configuration and Monitoring Dashboard
3.4 Important Transactions and Control Tables
3.4.1 Mass Transfer ID and Schema GUID
3.4.2 Important Replication-Relevant Tables
3.4.3 Table Structure in SAP HANA Modeler
3.4.4 Data Transformation Capabilities within SAP Landscape Transformation Replication Server
3.5 Sizing and Basic Job Handling
3.5.1 Sizing of SAP LT Replication Server - Basic Rules and Influencing Factors
3.5.2 Important SAP LT Replication Server Jobs
3.5.3 Stopping Jobs
3.5.4 Restarting Jobs
3.6 Changing Load and Replication Procedures
3.6.1 Changing the number of Jobs
3.6.2 Embedded Health Checks
3.6.3 Performance Improvements for the Initial Load of Tables
3.7 Monitoring of Load and Replication Process
3.7.1 Status of Jobs and Connections
3.7.2 Status of Triggers
3.7.4 Using the Monitoring Transaction LTRO
3.7.5 Monitoring using SAP Solution Manager
3.8 Backup and Recovery Aspects
CUSTOMER SAP Landscape Transformation Replication Server
4 © 2016 SAP AG. All rights reserved. Table of Contents4 SAP Landscape Transformation Replication Server Cockpit
4.2 Starting and Stopping all Configurations
4.3 Prerequisites: Choosing a Mass Transfer ID
4.4 Navigating from the SAP Landscape Transformation Replication Server Cockpit
4.5 SAP Landscape Transformation Replication Server Cockpit Tab Pages
5 Special Considerations for Source Systems
5.1 Impact of Software Maintenance activities in ABAP Source Systems
5.2 Archiving Data in Source Systems
5.3 Preventing Archive Deletes from being Replicated to a Target System
5.4 Performance Implications in Source System using Trigger-based Data Replication
5.5 Improving Performance for Configurations with Many Tables and Low Change Rates
5.6 Data Volume Management
6 Replication Logging
6.3 Changing the Replication Logging Settings
6.3.1 Operational Considerations
7 Frequently Asked Questions and Troubleshooting Recommendations
7.1 If SAP LT Replication Server for SAP HANA is already in use, what are the considerations when applying a new DMIS version and/or support package?
7.2 Does SAP LT Replication Server for SAP HANA only support 1:1 data replication or is it possible to do filtering (selective data replication) and / or transform data during the replication?
7.3 Are there any special considerations if the source system is a non-ABAP system?
7.4 Is it possible to use a configuration for multiple source and target SAP HANA systems?
7.5 What are the potential issues if the creation of a configuration and a related schema fails?
7.6 How can I ensure that data is consistent in the source system and SAP HANA system?
7.7 What happens in case of network failures?
7.8 Is the partitioning of SAP HANA tables supported by SAP LT Replication Server?
7.9 Does SAP LT Replication Server for SAP HANA support data compression like the SAP HANA database?
7.10 How to use Authorization Groups to control access on configuration level by LT Replication Server administration tasks?
7.11 How to define an alternative connection for the initial load?
7.12 How to change the settings of the DB connection to the target system?
7.13 The Notification Console
8.1 SAP Landscape Transformation Replication Server on SAP Community Network (SCN)
8.2 Related Guides
8.3 Related SAP Notes
Caution This guide does not replace the daily operations handbook that we recommend customers to create for their specific production operations.
Designing, implementing, and running your SAP applications at peak performance 24 hours a day has never been more vital for your business success than now.
This guide provides a starting point for managing your SAP applications and maintaining and running them optimally. It contains specific information for various tasks and lists the tools that you can use to implement them.
This guide also provides references to the documentation required for these tasks, so you will sometimes also need other Guides such as the Master Guide, Technical Infrastructure Guide, and SAP Library.
Target Groups Technical Consultants System Administrators Solution Consultants Business Process Owner Support Specialist
SAP Application A SAP application is an SAP software solution that serves a specific business area like ERP, CRM, PLM, SRM, and SCM.
Business Scenario From a microeconomic perspective, a business scenario is a cycle, which consists of several different interconnected logical processes in time. Typically, a business scenario includes several company departments and involves with other business partners. From a technical point of view, a business scenario needs at least one SAP application (SAP ERP, SAP SCM, or others) for each cycle and possibly other third-party systems. A business scenario is a unit which can be implemented separately and reflects the customer’s prospective course of business.
The SAP Landscape Transformation (SAP LT) Replication Server is the SAP technology that allows you to load and replicate data in real-time from ABAP source systems and non- ABAP source systems to an SAP HANA environment.
The SAP LT Replication Server uses a trigger-based replication approach to pass data from the source system to the target system.
The SAP LT Replication Server can be installed either as a separate SAP system, or if the technical prerequisites permit, on an ABAP source system.
In order to replicate data, you must first define the parameters that the SAP LT Replication Server will use to replicate data from one or more source systems to one or more target systems. You specify this information in a Configuration. A configuration contains information about the source system, the target system, and the relevant connections. You define configurations in the SAP LT Replication Server.
You use a configuration to load and replicate data from one source system to one target database schema of a HANA system (1:1), or from multiple source systems to one target database schema of an SAP HANA system (N:1). Furthermore, it is possible to load and replicate data from one source system to multiple (up to 4) target database schemas of one or more HANA systems (1:N). You can also specify the type of data load and replication
- either in real-time, or scheduled by time or by interval.
The trigger-based data replication approach is a table-based concept that retrieves data from application tables in the source system (or source systems). A user uses the SAP HANA Studio to select the tables for the replication.
If not all data records of a table should be transferred, you can create transformation rules to selectively filter the data (selective data replication) or to enable other transformations during the data replication process.
The following graphic outlines the basic concept and the typical landscape (for an ABAP source system) using the
trigger-based data replication approach of the SAP LT Replication Server:
The SAP LT Replication Server can be used for data replication from ABAP source systems and non- ABAP source systems to the SAP HANA system. In the Configuration & Monitoring Dashboard (transaction LTR) of the SAP LT Replication Server, you can define a new configuration that contains the relevant information required to create the connection between the source systems and the target SAP HANA systems.
The technical landscape consists of following components:
ABAP source system (or systems) The source system tracks database changes by using database triggers. It records information about changes in the logging tables. Read modules (located on the ABAP source system) transfer the data from the source system to the SAP LT Replication Server. The relevant data is read from the application tables.
Non-ABAP source system (or systems) The non- ABAP source system tracks database changes by using database triggers. It records information about changes in the logging tables. Read modules (located at the SAP LT Replication Server) transfer the data from the non-ABAP source system to the SAP LT Replication Server. The relevant data is read from the application tables.
SAP LT Replication Server An SAP system that facilitates the replication of data from one or more source systems to one or more target systems. The source systems can be SAP or non- ABAP systems.
SAP HANA system The SAP HANA system contains the SAP HANA database. It is used to store the replicated data. The SAP LT Replication Server and the SAP HANA system communicate by means of a database connection.
Prior to the installation, it is important to understand the various system landscape options available: