API for AWS Cloud Map¶

ABAP Package	`/AWS1/API_SDY_IMPL`
ABAP SDK "TLA"	`SDY`
ABAP Interface	`/AWS1/IF_SDY`

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 AWS Cloud Map is SDY. 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 ServiceDiscovery 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¶

Cloud Map

With Cloud Map, you can configure public DNS, private DNS, or HTTP namespaces that your microservice applications run in. When an instance becomes available, you can call the Cloud Map API to register the instance with Cloud Map. For public or private DNS namespaces, Cloud Map automatically creates DNS records and an optional health check. Clients that submit public or private DNS queries, or HTTP requests, for the service receive an answer that contains up to eight healthy records.

Using the SDK¶

In your code, create a client using the SDK module for AWS Cloud Map, which is created with factory method /AWS1/CL_SDY_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_sdy)       = /aws1/cl_sdy_factory=>create( go_session ).

Your variable go_sdy is an instance of /AWS1/IF_SDY, and all of the operations in the AWS Cloud Map service are accessed by calling methods in /AWS1/IF_SDY.

API Operations¶

For an overview of ABAP method calls corresponding to API operations in AWS Cloud Map, see the Operation List.

Factory Method¶

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

Creates an object of type /AWS1/IF_SDY.

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_SDY` `/AWS1/IF_SDY`¶

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

Configuring Programmatically¶

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

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

Paginators¶

Paginators for AWS Cloud Map can be created via get_paginator() which returns a paginator object of type /AWS1/IF_SDY_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 AWS Cloud Map can be found in interface /AWS1/IF_SDY_PAGINATOR.