API for Amazon Chime SDK Media Pipelines¶

ABAP Package	`/AWS1/API_CHP_IMPL`
ABAP SDK "TLA"	`CHP`
ABAP Interface	`/AWS1/IF_CHP`

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 Chime SDK Media Pipelines is CHP. 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 Chime SDK Media Pipelines 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 Chime SDK media pipeline APIs in this section allow software developers to create Amazon Chime SDK media pipelines that capture, concatenate, or stream your Amazon Chime SDK meetings. For more information about media pipelines, see Amazon Chime SDK media pipelines.

Using the SDK¶

In your code, create a client using the SDK module for Amazon Chime SDK Media Pipelines, which is created with factory method /AWS1/CL_CHP_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_chp)       = /aws1/cl_chp_factory=>create( go_session ).

Your variable go_chp is an instance of /AWS1/IF_CHP, and all of the operations in the Amazon Chime SDK Media Pipelines service are accessed by calling methods in /AWS1/IF_CHP.

API Operations¶

For an overview of ABAP method calls corresponding to API operations in Amazon Chime SDK Media Pipelines, see the Operation List.

Factory Method¶

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

Creates an object of type /AWS1/IF_CHP.

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_CHP` `/AWS1/IF_CHP`¶

/AWS1/IF_CHP represents the ABAP client for the Chime SDK Media Pipelines service, representing each operation as a method call. For more information see the API Page page.

Configuring Programmatically¶

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

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

Paginators¶

Paginators for Amazon Chime SDK Media Pipelines can be created via get_paginator() which returns a paginator object of type /AWS1/IF_CHP_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 Amazon Chime SDK Media Pipelines can be found in interface /AWS1/IF_CHP_PAGINATOR.