API for Amazon Chime SDK Meetings¶

ABAP Package	`/AWS1/API_CHM_IMPL`
ABAP SDK "TLA"	`CHM`
ABAP Interface	`/AWS1/IF_CHM`

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 Meetings is CHM. 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 Meetings 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 meetings APIs in this section allow software developers to create Amazon Chime SDK meetings, set the Amazon Web Services Regions for meetings, create and manage users, and send and receive meeting notifications. For more information about the meeting APIs, see Amazon Chime SDK meetings.

Using the SDK¶

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

Your variable go_chm is an instance of /AWS1/IF_CHM, and all of the operations in the Amazon Chime SDK Meetings service are accessed by calling methods in /AWS1/IF_CHM.

API Operations¶

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

Factory Method¶

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

Creates an object of type /AWS1/IF_CHM.

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_CHM` `/AWS1/IF_CHM`¶

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

Configuring Programmatically¶

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

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

Paginators¶

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