API for Amazon Managed Blockchain Query¶

ABAP Package	`/AWS1/API_MBQ_IMPL`
ABAP SDK "TLA"	`MBQ`
ABAP Interface	`/AWS1/IF_MBQ`

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 Managed Blockchain Query is MBQ. 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 ManagedBlockchain Query 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 Blockchain (AMB) Query provides you with convenient access to multi-blockchain network data, which makes it easier for you to extract contextual data related to blockchain activity. You can use AMB Query to read data from public blockchain networks, such as Bitcoin Mainnet and Ethereum Mainnet. You can also get information such as the current and historical balances of addresses, or you can get a list of blockchain transactions for a given time period. Additionally, you can get details of a given transaction, such as transaction events, which you can further analyze or use in business logic for your applications.

Using the SDK¶

In your code, create a client using the SDK module for Amazon Managed Blockchain Query, which is created with factory method /AWS1/CL_MBQ_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_mbq)       = /aws1/cl_mbq_factory=>create( go_session ).

Your variable go_mbq is an instance of /AWS1/IF_MBQ, and all of the operations in the Amazon Managed Blockchain Query service are accessed by calling methods in /AWS1/IF_MBQ.

API Operations¶

For an overview of ABAP method calls corresponding to API operations in Amazon Managed Blockchain Query, see the Operation List.

Factory Method¶

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

Creates an object of type /AWS1/IF_MBQ.

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_MBQ` `/AWS1/IF_MBQ`¶

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

Configuring Programmatically¶

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

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

Paginators¶

Paginators for Amazon Managed Blockchain Query can be created via get_paginator() which returns a paginator object of type /AWS1/IF_MBQ_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 Managed Blockchain Query can be found in interface /AWS1/IF_MBQ_PAGINATOR.