API for AWS re:Post Private¶

ABAP Package	`/AWS1/API_RPP_IMPL`
ABAP SDK "TLA"	`RPP`
ABAP Interface	`/AWS1/IF_RPP`

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 re:Post Private is RPP. 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 repostspace 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¶

AWS re:Post Private is a private version of AWS re:Post for enterprises with Enterprise Support or Enterprise On-Ramp Support plans. It provides access to knowledge and experts to accelerate cloud adoption and increase developer productivity. With your organization-specific private re:Post, you can build an organization-specific developer community that drives efficiencies at scale and provides access to valuable knowledge resources. Additionally, re:Post Private centralizes trusted AWS technical content and offers private discussion forums to improve how your teams collaborate internally and with AWS to remove technical obstacles, accelerate innovation, and scale more efficiently in the cloud.

Using the SDK¶

In your code, create a client using the SDK module for AWS re:Post Private, which is created with factory method /AWS1/CL_RPP_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_rpp)       = /aws1/cl_rpp_factory=>create( go_session ).

Your variable go_rpp is an instance of /AWS1/IF_RPP, and all of the operations in the AWS re:Post Private service are accessed by calling methods in /AWS1/IF_RPP.

API Operations¶

For an overview of ABAP method calls corresponding to API operations in AWS re:Post Private, see the Operation List.

Factory Method¶

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

Creates an object of type /AWS1/IF_RPP.

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_RPP` `/AWS1/IF_RPP`¶

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

Configuring Programmatically¶

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

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

Paginators¶

Paginators for AWS re:Post Private can be created via get_paginator() which returns a paginator object of type /AWS1/IF_RPP_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 re:Post Private can be found in interface /AWS1/IF_RPP_PAGINATOR.