API for Amazon Data Lifecycle Manager¶

ABAP Package	`/AWS1/API_DLM_IMPL`
ABAP SDK "TLA"	`DLM`
ABAP Interface	`/AWS1/IF_DLM`

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 Amazon Data Lifecycle Manager is DLM. 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 DLM 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¶

Amazon Data Lifecycle Manager

With Amazon Data Lifecycle Manager, you can manage the lifecycle of your Amazon Web Services resources. You create lifecycle policies, which are used to automate operations on the specified resources.

Amazon Data Lifecycle Manager supports Amazon EBS volumes and snapshots. For information about using Amazon Data Lifecycle Manager with Amazon EBS, see Amazon Data Lifecycle Manager in the Amazon EC2 User Guide.

Using the SDK¶

In your code, create a client using the SDK module for Amazon Data Lifecycle Manager, which is created with factory method /AWS1/CL_DLM_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_dlm)       = /aws1/cl_dlm_factory=>create( go_session ).

Your variable go_dlm is an instance of /AWS1/IF_DLM, and all of the operations in the Amazon Data Lifecycle Manager service are accessed by calling methods in /AWS1/IF_DLM.

API Operations¶

For an overview of ABAP method calls corresponding to API operations in Amazon Data Lifecycle Manager, see the Operation List.

Factory Method¶

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

Creates an object of type /AWS1/IF_DLM.

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_DLM` `/AWS1/IF_DLM`¶

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

Configuring Programmatically¶

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

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