API for AWS Elemental MediaLive¶

ABAP Package	`/AWS1/API_MDL`
ABAP SDK "TLA"	`MDL`
ABAP Interface	`/AWS1/IF_MDL`

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 Elemental MediaLive is MDL. 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 MediaLive 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¶

API for AWS Elemental MediaLive

Using the SDK¶

In your code, create a client using the SDK module for AWS Elemental MediaLive, which is created with factory method /AWS1/CL_MDL_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_mdl)       = /aws1/cl_mdl_factory=>create( go_session ).

Your variable go_mdl is an instance of /AWS1/IF_MDL, and all of the operations in the AWS Elemental MediaLive service are accessed by calling methods in /AWS1/IF_MDL.

API Operations¶

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

Factory Method¶

`/AWS1/CL_MDL_FACTORY=>CREATE( )`¶

Creates an object of type /AWS1/IF_MDL.

IMPORTING¶

Required arguments:¶

`IO_SESSION` `TYPE REF TO` `/AWS1/CL_RT_SESSION_BASE`¶

Optional arguments:¶

`IV_PROTOCOL` `TYPE` `/AWS1/RT_PROTOCOL`¶

`IV_REGION` `TYPE` `/AWS1/RT_REGION_ID`¶

`IV_CUSTOM_ENDPOINT` `TYPE` `/AWS1/RT_ENDPOINT`¶

RETURNING¶

`OO_CLIENT` `TYPE REF TO` `/AWS1/IF_MDL`¶

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