API for Amazon Kinesis Analytics¶

ABAP Package	`/AWS1/API_KN2_IMPL`
ABAP SDK "TLA"	`KN2`
ABAP Interface	`/AWS1/IF_KN2`

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 Kinesis Analytics is KN2. 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 Kinesis Analytics V2 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¶

Amazon Managed Service for Apache Flink was previously known as Amazon Kinesis Data Analytics for Apache Flink.

Amazon Managed Service for Apache Flink is a fully managed service that you can use to process and analyze streaming data using Java, Python, SQL, or Scala. The service enables you to quickly author and run Java, SQL, or Scala code against streaming sources to perform time series analytics, feed real-time dashboards, and create real-time metrics.

Using the SDK¶

In your code, create a client using the SDK module for Amazon Kinesis Analytics, which is created with factory method /AWS1/CL_KN2_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_kn2)       = /aws1/cl_kn2_factory=>create( go_session ).

Your variable go_kn2 is an instance of /AWS1/IF_KN2, and all of the operations in the Amazon Kinesis Analytics service are accessed by calling methods in /AWS1/IF_KN2.

API Operations¶

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

Factory Method¶

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

Creates an object of type /AWS1/IF_KN2.

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_KN2` `/AWS1/IF_KN2`¶

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

Configuring Programmatically¶

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

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

Paginators¶

Paginators for Amazon Kinesis Analytics can be created via get_paginator() which returns a paginator object of type /AWS1/IF_KN2_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 Kinesis Analytics can be found in interface /AWS1/IF_KN2_PAGINATOR.