API for Amazon CloudWatch Evidently¶

ABAP Package	`/AWS1/API_EVY_IMPL`
ABAP SDK "TLA"	`EVY`
ABAP Interface	`/AWS1/IF_EVY`

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 CloudWatch Evidently is EVY. 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 Evidently 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¶

You can use Amazon CloudWatch Evidently to safely validate new features by serving them to a specified percentage of your users while you roll out the feature. You can monitor the performance of the new feature to help you decide when to ramp up traffic to your users. This helps you reduce risk and identify unintended consequences before you fully launch the feature.

You can also conduct A/B experiments to make feature design decisions based on evidence and data. An experiment can test as many as five variations at once. Evidently collects experiment data and analyzes it using statistical methods. It also provides clear recommendations about which variations perform better. You can test both user-facing features and backend features.

Using the SDK¶

In your code, create a client using the SDK module for Amazon CloudWatch Evidently, which is created with factory method /AWS1/CL_EVY_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_evy)       = /aws1/cl_evy_factory=>create( go_session ).

Your variable go_evy is an instance of /AWS1/IF_EVY, and all of the operations in the Amazon CloudWatch Evidently service are accessed by calling methods in /AWS1/IF_EVY.

API Operations¶

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

Factory Method¶

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

Creates an object of type /AWS1/IF_EVY.

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_EVY` `/AWS1/IF_EVY`¶

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

Configuring Programmatically¶

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

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

Paginators¶

Paginators for Amazon CloudWatch Evidently can be created via get_paginator() which returns a paginator object of type /AWS1/IF_EVY_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 CloudWatch Evidently can be found in interface /AWS1/IF_EVY_PAGINATOR.