API for Lambda Web¶

ABAP Package	`/AWS1/API_LMW`
ABAP SDK "TLA"	`LMW`
ABAP Interface	`/AWS1/IF_LMW`

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 Lambda Web is LMW. 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 Lambda Web 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 Lambda Web Functions APIs (LambdaWeb namespace) are experimental and for internal AWS use only. They are not yet available to external customers.

AWS Lambda Web Functions let you run web applications and APIs as HTTP servers on Lambda. A web function has one or more immutable revisions (code and configuration) and one or more endpoints that expose it over HTTPS.

Using the SDK¶

In your code, create a client using the SDK module for Lambda Web, which is created with factory method /AWS1/CL_LMW_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_lmw)       = /aws1/cl_lmw_factory=>create( go_session ).

Your variable go_lmw is an instance of /AWS1/IF_LMW, and all of the operations in the Lambda Web service are accessed by calling methods in /AWS1/IF_LMW.

API Operations¶

For an overview of ABAP method calls corresponding to API operations in Lambda Web, see the Operation List.

Factory Method¶

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

Creates an object of type /AWS1/IF_LMW.

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_lmw` `/AWS1/IF_LMW`¶

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

Configuring Programmatically¶

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

lo_config is a variable of type /AWS1/CL_LMW_CONFIG. See the documentation for /AWS1/CL_LMW_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_LMW_WAITER.

Paginators¶

Paginators for Lambda Web can be created via get_paginator() which returns a paginator object of type /AWS1/IF_LMW_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 Lambda Web can be found in interface /AWS1/IF_LMW_PAGINATOR.