API for AWS Outposts¶
| ABAP Package | /AWS1/API_OUT_IMPL |
|---|---|
| ABAP SDK "TLA" | OUT |
| ABAP Interface | /AWS1/IF_OUT |
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 Outposts is OUT.
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 Outposts 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 Web Services Outposts is a fully managed service that extends Amazon Web Services infrastructure, APIs, and tools to customer premises. By providing local access to Amazon Web Services managed infrastructure, Amazon Web Services Outposts enables customers to build and run applications on premises using the same programming interfaces as in Amazon Web Services Regions, while using local compute and storage resources for lower latency and local data processing needs.
Using the SDK¶
In your code, create a client using the SDK module for AWS Outposts, which is created with
factory method /AWS1/CL_OUT_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_out) = /aws1/cl_out_factory=>create( go_session ).
Your variable go_out is an instance of /AWS1/IF_OUT,
and all of the operations
in the AWS Outposts service are accessed by calling methods in /AWS1/IF_OUT.
API Operations¶
For an overview of ABAP method calls corresponding to API operations in AWS Outposts, see the Operation List.
Factory Method¶
/AWS1/CL_OUT_FACTORY=>create( )¶
Creates an object of type /AWS1/IF_OUT.
IMPORTING¶
Optional arguments:¶
iv_protocol TYPE /aws1/rt_protocol /AWS1/RT_PROTOCOL¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
io_session TYPE REF TO /aws1/cl_rt_session_base /AWS1/CL_RT_SESSION_BASE¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
iv_region TYPE /aws1/rt_region_id /AWS1/RT_REGION_ID¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
iv_custom_endpoint TYPE /aws1/rt_endpoint /AWS1/RT_ENDPOINT¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
RETURNING¶
oo_client TYPE REF TO /aws1/if_out /AWS1/IF_OUT¶
/AWS1/IF_OUTrepresents the ABAP client for the Outposts service, representing each operation as a method call. For more information see the API Page page.
Configuring Programmatically¶
DATA(lo_config) = DATA(go_out)->get_config( ).
lo_config is a variable of type /AWS1/CL_OUT_CONFIG. See the documentation for /AWS1/CL_OUT_CONFIG for
details on the settings that can be configured.
Paginators¶
Paginators for AWS Outposts can be created via `get_paginator()` which returns a paginator object of type [`/AWS1/IF_OUT_PAGINATOR`](./_AWS1_IF_OUT_PAGINATOR.md). 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 Outposts can be found in interface [`/AWS1/IF_OUT_PAGINATOR`](./_AWS1_IF_OUT_PAGINATOR.md).