API for AWS Server Migration Service¶

ABAP Package	`/AWS1/API_SMS_IMPL`
ABAP SDK "TLA"	`SMS`
ABAP Interface	`/AWS1/IF_SMS`

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 Server Migration Service is SMS. 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 SMS 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¶

Product update

We recommend Amazon Web Services Application Migration Service (Amazon Web Services MGN) as the primary migration service for lift-and-shift migrations. If Amazon Web Services MGN is unavailable in a specific Amazon Web Services Region, you can use the Server Migration Service APIs through March 2023.

Server Migration Service (Server Migration Service) makes it easier and faster for you to migrate your on-premises workloads to Amazon Web Services. To learn more about Server Migration Service, see the following resources:

Using the SDK¶

In your code, create a client using the SDK module for AWS Server Migration Service, which is created with factory method /AWS1/CL_SMS_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_sms)       = /aws1/cl_sms_factory=>create( go_session ).

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

API Operations¶

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

Factory Method¶

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

Creates an object of type /AWS1/IF_SMS.

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_SMS` `/AWS1/IF_SMS`¶

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

Configuring Programmatically¶

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

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

Paginators¶

Paginators for AWS Server Migration Service can be created via get_paginator() which returns a paginator object of type /AWS1/IF_SMS_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 Server Migration Service can be found in interface /AWS1/IF_SMS_PAGINATOR.