API for AWS Database Migration Service¶

ABAP Package	`/AWS1/API_DMG_IMPL`
ABAP SDK "TLA"	`DMG`
ABAP Interface	`/AWS1/IF_DMG`

The "TLA" is a Three Letter Abbreviation that appears in ABAP class names, data dictionary objects and other ABAP objects throughout the AWS SDK for SAP ABAP. The TLA for AWS Database Migration Service is DMG. This TLA helps squeeze ABAP objects into the 30-character length limit of the ABAP data dictionary.

Installation¶

To install the AWS SDK for SAP ABAP, import the Core transport, along with the transport for the Database Migration Service module and other API modules you are interested in. A few modules are included in the Core transport itself. For more information, see the Developer Guide guide.

About The Service¶

Database Migration Service

Database Migration Service (DMS) can migrate your data to and from the most widely used commercial and open-source databases such as Oracle, PostgreSQL, Microsoft SQL Server, Amazon Redshift, MariaDB, Amazon Aurora, MySQL, and SAP Adaptive Server Enterprise (ASE). The service supports homogeneous migrations such as Oracle to Oracle, as well as heterogeneous migrations between different database platforms, such as Oracle to MySQL or SQL Server to PostgreSQL.

For more information about DMS, see What Is Database Migration Service? in the Database Migration Service User Guide.

Using the SDK¶

In your code, create a client using the SDK module for AWS Database Migration Service, which is created with factory method /AWS1/CL_DMG_FACTORY=>create(). In this example we will assume you have configured an SDK profile in transaction /AWS1/IMG called ZFINANCE.

DATA(go_session)   = /aws1/cl_rt_session_aws=>create( 'ZFINANCE' ).
DATA(go_dmg)       = /aws1/cl_dmg_factory=>create( go_session ).

Your variable go_dmg is an instance of /AWS1/IF_DMG, and all of the operations in the AWS Database Migration Service service are accessed by calling methods in /AWS1/IF_DMG.

API Operations¶

For an overview of ABAP method calls corresponding to API operations in AWS Database Migration Service, see the Operation List.

Factory Method¶

`/AWS1/CL_DMG_FACTORY=>create( )`¶

Creates an object of type /AWS1/IF_DMG.

IMPORTING¶

Optional arguments:¶

`IV_PROTOCOL` `TYPE /AWS1/RT_PROTOCOL` `/AWS1/RT_PROTOCOL`¶

`IO_SESSION` `TYPE REF TO /AWS1/CL_RT_SESSION_BASE` `/AWS1/CL_RT_SESSION_BASE`¶

`IV_REGION` `TYPE /AWS1/RT_REGION_ID` `/AWS1/RT_REGION_ID`¶

`IV_CUSTOM_ENDPOINT` `TYPE /AWS1/RT_ENDPOINT` `/AWS1/RT_ENDPOINT`¶

RETURNING¶

`OO_CLIENT` `TYPE REF TO /AWS1/IF_DMG` `/AWS1/IF_DMG`¶

/AWS1/IF_DMG represents the ABAP client for the Database Migration Service service, representing each operation as a method call. For more information see the API Page page.

Configuring Programmatically¶

DATA(lo_config) = DATA(go_dmg)->get_config( ).

lo_config is a variable of type /AWS1/CL_DMG_CONFIG. See the documentation for /AWS1/CL_DMG_CONFIG for details on the settings that can be configured.

Waiters¶

Waiters for Implementation can be accessed via get_waiter() method followed by the waiter method to be called.

Details about the waiter methods available for service Implementation can be found in interface /AWS1/IF_DMG_WAITER.

Paginators¶

Paginators for AWS Database Migration Service can be created via get_paginator() which returns a paginator object of type /AWS1/IF_DMG_PAGINATOR. The operation method that is being paginated is called using the paginator object, which accepts any necessary parameters to provide to the underlying API operation. This returns an iterator object which can be used to iterate over paginated results using has_next() and get_next() methods.

Details about the paginator methods available for service AWS Database Migration Service can be found in interface /AWS1/IF_DMG_PAGINATOR.