Describing the Architecture for Replication to Non-SAP Databases

Objective

After completing this lesson, you will be able to understand the replication of data to non-SAP databases.

Replication of Data to Non-SAP Databases

Architecture, configuration, and their features are similar to the use cases that were covered by SAP HANA as a target system. However, a separate SLT license is required. The OS and DB restrictions of the target database are the same as the OS and DB restrictions of SAP NetWeaver 7.02 or higher. For more information, see the product availability matrix on the SAP Service Marketplace.

A diagram shows data replication from ABAP Source System to Non-ABAP Target via SAP LT Replication Server. It depicts DB triggers, RFC and DB connections, and engines for read, write, mapping.

Due to the use of OPEN SQL in the function modules generated by SLT which are used to write the data to the target system, the supported non-ABAP-based targets are restricted to the databases officially supported by SAP NetWeaver. The supported DB versions are further dependent on the SAP NetWeaver release and the related DBSL version installed on the SAP LT Replication Server instance. See details in the Product Availability Matrix.

Note

See also SAP Note 2737003 for the details and the list of databases that can be connected as a non-ABAP-based target to SLT 2.0 (DMIS 2011) / SLT 3.0 (DMIS 2018).

Note

When the target of your SLT replication is hosted in an Infrastructure as a Service environment, it may be necessary to have the SLT system also run in the IaaS environment to ensure a stable connection to the target database. (see SAP Note 1380654 - SAP support in IaaS environments).

Diagram of SAP LT Replication: Data flows from non-ABAP source system through read, mapping, and write engines on replication server to non-ABAP target system. DB connections are shown.

Check with SAP DMLT Global Customer Engagement (sap_dmlt_gce@sap.com) whether this setup can be supported by SAP for your SLT version.

Note

See also SAP Note 1768805 for limitations on non-SAP source systems.

Diagram showing data flow between systems: ABAP/Non-ABAP Source system connects to SLT System via RFC/DB Connection, which connects to Non-SAP Database through DB Connection, illustrating SAP replication.

The database user of the target database must have authorizations to write data to the database and to create objects such as views and synonyms (depending on the database used).

Similar to SAP HANA as a target database, SLT creates the respective table in the target database of a non-SAP database. However, SLT does not create a schema in the case of a non-SAP database.

For authorizations required in the source system and the SLT Server, see previous units in this course and the Security Guide on the SAP Help Portal.

An image shows SLT deployment options: recommended separate instance compared to instance on source (NW 7.02+).

All ABAP source systems require the installation of DMIS 2011 or 2018. Remember to keep the support packages of DMIS 2011 add-on in sync.

However, SAP generally supports a support package level in the ABAP source systems that is up to three stacks lower than the central instance (the SLT server) that manages the replication. For example, if the central instance is on DMIS 2018 SP03, the target and source system add-on require at least DMIS 2018 SP00.

Next lesson