The SAP LT Replication Server is installed as an add-on to any SAP source and/or to the SAP LT Replication Server system.
Installing the Data Migration Server (DMIS) add-on makes certain user roles and functionalities available. Let’s take a look at how to do this.
Before you can provision your data via the SAP LT Replication Server, you must decide on the installation type that best suits your needs and your environment. The primary elements of your landscape are the source system(s) (both non-ABAP and ABAP), the SAP LT Replication Server system, and the SAP HANA target system. We’ll cover the connections between these systems later in greater detail.
The following are the basic requirements for the SAP LT Replication Server:
- SAP NetWeaver 7.02 or greater
- SAP Kernel 7.20 patch level 110 or higher
- Same or higher SAP Basis release than all connected systems
You can also find detailed sizing information from SAP in the Sizing Guide, but you’ll need to know your SAP Basis version.
When your source is an SAP system, the SAP LT Replication Server can be installed on its own separate system or on the source system. For a non-SAP source system, the SAP LT Replication Server cannot be installed on the source. In the following sections, we’ll look at these three installation scenarios.
ABAP Source System
In the first scenario, as shown in the figure below, the SAP LT Replication Server is installed directly on the SAP source system, provided the source system meets all the requirements listed earlier. When changes occur in the source system, these changes are recorded in the logging tables. The read module, which is located on the source, then transfers the data.
While using a source SAP system or another SAP NetWeaver system could seem like a simpler, less costly solution, the SAP LT Replication Server replicates data through background processing, so CPU load is an important factor to consider.
Separate Server with an ABAP Source System
Another option when replicating data from an ABAP source is installing the SAP LT Replication Server on a separate server, as shown in the following figure. This separate server could be a dedicated instance or another SAP NetWeaver system. As with the previous scenario, changes are captured in logging tables and moved via the read module. This option is best if you have an ABAP source system, but that source system does not meet the prerequisites for hosting the SAP LT Replication Server.
When using a separate SAP LT Replication Server, SAP recommends ensuring that the server system and the source system are on the same Support Pack (SP) when possible to ensure that all current functionality is available.
Separate Server with a Non-ABAP Source System
Typically, customers use a separate server for the SAP LT Replication Server. This division prevents software dependencies during maintenance activities and reduces performance impact on the source system. The main difference between using ABAP versus non-ABAP sources with a separate server for the SAP LT Replication Server is that the read module is on the SAP LT Replication Server instead of on the source system in a non-ABAP landscape.
Additionally, the SAP LT Replication Server will use a database connection from the source whereas with an ABAP system, the SAP LT Replication Server uses a Remote Function Call (RFC) connection. This option is shown in the final figure.
These scenarios are all viable options for installing the SAP LT Replication Server, and your decision will be based on your initial system landscape. When deciding on an installation strategy, consider the sources of your data and what your primary needs and concerns are. Learn more about SAP's data management capabilities here.
Editor’s note: This post has been adapted from a section of the book Data Provisioning for SAP HANA by Megan Cundiff, Vernon Gomes, Russell Lamb, Don Loden, and Vinay Suneja.