API for Amazon EventBridge Pipes¶

ABAP Package	`/AWS1/API_PIS_IMPL`
ABAP SDK "TLA"	`PIS`
ABAP Interface	`/AWS1/IF_PIS`

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 EventBridge Pipes is PIS. 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 Pipes 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 EventBridge Pipes connects event sources to targets. Pipes reduces the need for specialized knowledge and integration code when developing event driven architectures. This helps ensures consistency across your company’s applications. With Pipes, the target can be any available EventBridge target. To set up a pipe, you select the event source, add optional event filtering, define optional enrichment, and select the target for the event data.

Using the SDK¶

In your code, create a client using the SDK module for Amazon EventBridge Pipes, which is created with factory method /AWS1/CL_PIS_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_pis)       = /aws1/cl_pis_factory=>create( go_session ).

Your variable go_pis is an instance of /AWS1/IF_PIS, and all of the operations in the Amazon EventBridge Pipes service are accessed by calling methods in /AWS1/IF_PIS.

API Operations¶

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

Factory Method¶

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

Creates an object of type /AWS1/IF_PIS.

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_PIS` `/AWS1/IF_PIS`¶

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

Configuring Programmatically¶

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

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

Paginators¶

Paginators for Amazon EventBridge Pipes can be created via get_paginator() which returns a paginator object of type /AWS1/IF_PIS_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 EventBridge Pipes can be found in interface /AWS1/IF_PIS_PAGINATOR.