API for AWS MediaTailor¶

ABAP Package	`/AWS1/API_MDT_IMPL`
ABAP SDK "TLA"	`MDT`
ABAP Interface	`/AWS1/IF_MDT`

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 MediaTailor is MDT. 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 MediaTailor 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¶

Use the AWS Elemental MediaTailor SDKs and CLI to configure scalable ad insertion and linear channels. With MediaTailor, you can assemble existing content into a linear stream and serve targeted ads to viewers while maintaining broadcast quality in over-the-top (OTT) video applications. For information about using the service, including detailed information about the settings covered in this guide, see the AWS Elemental MediaTailor User Guide.

Through the SDKs and the CLI you manage AWS Elemental MediaTailor configurations and channels the same as you do through the console. For example, you specify ad insertion behavior and mapping information for the origin server and the ad decision server (ADS).

Using the SDK¶

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

Your variable go_mdt is an instance of /AWS1/IF_MDT, and all of the operations in the AWS MediaTailor service are accessed by calling methods in /AWS1/IF_MDT.

API Operations¶

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

Factory Method¶

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

Creates an object of type /AWS1/IF_MDT.

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_MDT` `/AWS1/IF_MDT`¶

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

Configuring Programmatically¶

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

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

Paginators¶

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