Skip to content

API for AWS Batch

ABAP Package /AWS1/API_BTC_IMPL
ABAP SDK "TLA" BTC
ABAP Interface /AWS1/IF_BTC

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 Batch is BTC. 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 Batch 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

Batch

Using Batch, you can run batch computing workloads on the Amazon Web Services Cloud. Batch computing is a common means for developers, scientists, and engineers to access large amounts of compute resources. Batch uses the advantages of the batch computing to remove the undifferentiated heavy lifting of configuring and managing required infrastructure. At the same time, it also adopts a familiar batch computing software approach. You can use Batch to efficiently provision resources d, and work toward eliminating capacity constraints, reducing your overall compute costs, and delivering results more quickly.

As a fully managed service, Batch can run batch computing workloads of any scale. Batch automatically provisions compute resources and optimizes workload distribution based on the quantity and scale of your specific workloads. With Batch, there's no need to install or manage batch computing software. This means that you can focus on analyzing results and solving your specific problems instead.

Using the SDK

In your code, create a client using the SDK module for AWS Batch, which is created with factory method /AWS1/CL_BTC_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_btc)       = /aws1/cl_btc_factory=>create( go_session ).

Your variable go_btc is an instance of /AWS1/IF_BTC, and all of the operations in the AWS Batch service are accessed by calling methods in /AWS1/IF_BTC.

API Operations

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

Factory Method

/AWS1/CL_BTC_FACTORY=>create( )

Creates an object of type /AWS1/IF_BTC.

IMPORTING

Optional arguments:

IV_PROTOCOL TYPE /AWS1/RT_PROTOCOL

IO_SESSION TYPE REF TO /AWS1/CL_RT_SESSION_BASE

IV_REGION TYPE /AWS1/RT_REGION_ID

IV_CUSTOM_ENDPOINT TYPE /AWS1/RT_ENDPOINT

RETURNING

OO_CLIENT TYPE REF TO /AWS1/IF_BTC

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

Configuring Programmatically

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

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

Paginators

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