API for Amazon NeptuneData¶

ABAP Package	`/AWS1/API_NED_IMPL`
ABAP SDK "TLA"	`NED`
ABAP Interface	`/AWS1/IF_NED`

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 NeptuneData is NED. 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 neptunedata 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¶

Neptune Data API

The Amazon Neptune data API provides SDK support for more than 40 of Neptune's data operations, including data loading, query execution, data inquiry, and machine learning. It supports the Gremlin and openCypher query languages, and is available in all SDK languages. It automatically signs API requests and greatly simplifies integrating Neptune into your applications.

Using the SDK¶

In your code, create a client using the SDK module for Amazon NeptuneData, which is created with factory method /AWS1/CL_NED_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_ned)       = /aws1/cl_ned_factory=>create( go_session ).

Your variable go_ned is an instance of /AWS1/IF_NED, and all of the operations in the Amazon NeptuneData service are accessed by calling methods in /AWS1/IF_NED.

API Operations¶

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

Factory Method¶

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

Creates an object of type /AWS1/IF_NED.

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_NED` `/AWS1/IF_NED`¶

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

Configuring Programmatically¶

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

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