API for AWSDeadlineCloud¶

ABAP Package	`/AWS1/API_TBD_IMPL`
ABAP SDK "TLA"	`TBD`
ABAP Interface	`/AWS1/IF_TBD`

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 AWSDeadlineCloud is TBD. 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 deadline 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 Deadline Cloud API provides infrastructure and centralized management for your projects. Use the Deadline Cloud API to onboard users, assign projects, and attach permissions specific to their job function.

With Deadline Cloud, content production teams can deploy resources for their workforce securely in the cloud, reducing the costs of added physical infrastructure. Keep your content production operations secure, while allowing your contributors to access the tools they need, such as scalable high-speed storage, licenses, and cost management services.

Using the SDK¶

In your code, create a client using the SDK module for AWSDeadlineCloud, which is created with factory method /AWS1/CL_TBD_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_tbd)       = /aws1/cl_tbd_factory=>create( go_session ).

Your variable go_tbd is an instance of /AWS1/IF_TBD, and all of the operations in the AWSDeadlineCloud service are accessed by calling methods in /AWS1/IF_TBD.

API Operations¶

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

Factory Method¶

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

Creates an object of type /AWS1/IF_TBD.

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_TBD` `/AWS1/IF_TBD`¶

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

Configuring Programmatically¶

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

lo_config is a variable of type /AWS1/CL_TBD_CONFIG. See the documentation for /AWS1/CL_TBD_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_TBD_WAITER.

Paginators¶

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