API for AWS Migration Hub¶

ABAP Package	`/AWS1/API_MHU_IMPL`
ABAP SDK "TLA"	`MHU`
ABAP Interface	`/AWS1/IF_MHU`

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 Migration Hub is MHU. 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 Migration Hub 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¶

The AWS Migration Hub API methods help to obtain server and application migration status and integrate your resource-specific migration tool by providing a programmatic interface to Migration Hub.

Remember that you must set your AWS Migration Hub home region before you call any of these APIs, or a HomeRegionNotSetException error will be returned. Also, you must make the API calls while in your home region.

Using the SDK¶

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

Your variable go_mhu is an instance of /AWS1/IF_MHU, and all of the operations in the AWS Migration Hub service are accessed by calling methods in /AWS1/IF_MHU.

API Operations¶

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

Factory Method¶

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

Creates an object of type /AWS1/IF_MHU.

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_MHU` `/AWS1/IF_MHU`¶

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

Configuring Programmatically¶

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

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

Paginators¶

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