API for Amazon Import/Export Snowball¶
ABAP Package | /AWS1/API_SNB_IMPL |
---|---|
ABAP SDK "TLA" | SNB |
ABAP Interface | /AWS1/IF_SNB |
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 Import/Export Snowball is SNB
.
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 Snowball 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 Amazon Web Services Snow Family provides a petabyte-scale data transport solution that uses secure devices to transfer large amounts of data between your on-premises data centers and Amazon Simple Storage Service (Amazon S3). The Snow Family commands described here provide access to the same functionality that is available in the Amazon Web Services Snow Family Management Console, which enables you to create and manage jobs for a Snow Family device. To transfer data locally with a Snow Family device, you'll need to use the Snowball Edge client or the Amazon S3 API Interface for Snowball or OpsHub for Snow Family. For more information, see the User Guide.
Using the SDK¶
In your code, create a client using the SDK module for Amazon Import/Export Snowball, which is created with
factory method /AWS1/CL_SNB_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_snb) = /aws1/cl_snb_factory=>create( go_session ).
Your variable go_snb
is an instance of /AWS1/IF_SNB
,
and all of the operations
in the Amazon Import/Export Snowball service are accessed by calling methods in /AWS1/IF_SNB
.
API Operations¶
For an overview of ABAP method calls corresponding to API operations in Amazon Import/Export Snowball, see the Operation List.
Factory Method¶
/AWS1/CL_SNB_FACTORY=>create( )
¶
Creates an object of type /AWS1/IF_SNB
.
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_SNB
/AWS1/IF_SNB
¶
/AWS1/IF_SNB
represents the ABAP client for the Snowball service, representing each operation as a method call. For more information see the API Page page.
Configuring Programmatically¶
DATA(lo_config) = DATA(go_snb)->get_config( ).
lo_config
is a variable of type /AWS1/CL_SNB_CONFIG
. See the documentation for /AWS1/CL_SNB_CONFIG
for
details on the settings that can be configured.
Paginators¶
Paginators for Amazon Import/Export Snowball can be created via `get_paginator()` which returns a paginator object of type [`/AWS1/IF_SNB_PAGINATOR`](./_AWS1_IF_SNB_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 Amazon Import/Export Snowball can be found in interface [`/AWS1/IF_SNB_PAGINATOR`](./_AWS1_IF_SNB_PAGINATOR.md).