API for Amazon Bedrock Agent Core Control Plane Fronting Layer¶
ABAP Package | /AWS1/API_BDO |
---|---|
ABAP SDK "TLA" | BDO |
ABAP Interface | /AWS1/IF_BDO |
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 Bedrock Agent Core Control Plane Fronting Layer is BDO
.
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 Bedrock AgentCore Control 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 Bedrock AgentCore is in preview release and is subject to change.
Amazon Bedrock Agent Core Control is a service that enables you to manage memory resources for your Amazon Bedrock agents.
Use this API to create, retrieve, update, and delete memory resources and their associated memory strategies. Memory resources enable your agents to store and retrieve information from conversations and interactions.
Using the SDK¶
In your code, create a client using the SDK module for Amazon Bedrock Agent Core Control Plane Fronting Layer, which is created with
factory method /AWS1/CL_BDO_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_bdo) = /aws1/cl_bdo_factory=>create( go_session ).
Your variable go_bdo
is an instance of /AWS1/IF_BDO
,
and all of the operations
in the Amazon Bedrock Agent Core Control Plane Fronting Layer service are accessed by calling methods in /AWS1/IF_BDO
.
API Operations¶
For an overview of ABAP method calls corresponding to API operations in Amazon Bedrock Agent Core Control Plane Fronting Layer, see the Operation List.
Factory Method¶
/AWS1/CL_BDO_FACTORY=>create( )
¶
Creates an object of type /AWS1/IF_BDO
.
IMPORTING¶
Optional arguments:¶
iv_protocol
TYPE /aws1/rt_protocol
/AWS1/RT_PROTOCOL
¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
io_session
TYPE REF TO /aws1/cl_rt_session_base
/AWS1/CL_RT_SESSION_BASE
¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
iv_region
TYPE /aws1/rt_region_id
/AWS1/RT_REGION_ID
¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
iv_custom_endpoint
TYPE /aws1/rt_endpoint
/AWS1/RT_ENDPOINT
¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
RETURNING¶
oo_client
TYPE REF TO /aws1/if_bdo
/AWS1/IF_BDO
¶
/AWS1/IF_BDO
represents the ABAP client for the Bedrock AgentCore Control service, representing each operation as a method call. For more information see the API Page page.
Configuring Programmatically¶
DATA(lo_config) = DATA(go_bdo)->get_config( ).
lo_config
is a variable of type /AWS1/CL_BDO_CONFIG
. See the documentation for /AWS1/CL_BDO_CONFIG
for
details on the settings that can be configured.
Waiters¶
Waiters for Implementation can be accessed via get_waiter()
method followed by the waiter method to be called.
Details about the waiter methods available for service Implementation can be found in interface /AWS1/IF_BDO_WAITER
.
Paginators¶
Paginators for Amazon Bedrock Agent Core Control Plane Fronting Layer can be created via get_paginator()
which returns a paginator object of type /AWS1/IF_BDO_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 Bedrock Agent Core Control Plane Fronting Layer can be found in interface /AWS1/IF_BDO_PAGINATOR
.