/AWS1/IF_BDO=>CREATEHARNESSENDPOINT()

About CreateHarnessEndpoint

Operation to create a harness endpoint.

Method Signature

METHODS /AWS1/IF_BDO~CREATEHARNESSENDPOINT
  IMPORTING
    !IV_HARNESSID TYPE /AWS1/BDOHARNESSID OPTIONAL
    !IV_ENDPOINTNAME TYPE /AWS1/BDOHARNESSENDPOINTNAME OPTIONAL
    !IV_TARGETVERSION TYPE /AWS1/BDOHARNESSVERSION OPTIONAL
    !IV_DESCRIPTION TYPE /AWS1/BDOHARNESSENDPOINTDESC OPTIONAL
    !IV_CLIENTTOKEN TYPE /AWS1/BDOCLIENTTOKEN OPTIONAL
    !IT_TAGS TYPE /AWS1/CL_BDOTAGSMAP_W=>TT_TAGSMAP OPTIONAL
  RETURNING
    VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_bdocreateharnendptrsp
  RAISING
    /AWS1/CX_BDOACCESSDENIEDEX
    /AWS1/CX_BDOCONFLICTEXCEPTION
    /AWS1/CX_BDOINTERNALSERVEREX
    /AWS1/CX_BDORESOURCENOTFOUNDEX
    /AWS1/CX_BDOSERVICEQUOTAEXCDEX
    /AWS1/CX_BDOTHROTTLINGEX
    /AWS1/CX_BDOVALIDATIONEX
    /AWS1/CX_BDOCLIENTEXC
    /AWS1/CX_BDOSERVEREXC
    /AWS1/CX_RT_TECHNICAL_GENERIC
    /AWS1/CX_RT_SERVICE_GENERIC.

IMPORTING

Required arguments:

iv_harnessid TYPE /AWS1/BDOHARNESSID /AWS1/BDOHARNESSID

The ID of the harness to create an endpoint for.

iv_endpointname TYPE /AWS1/BDOHARNESSENDPOINTNAME /AWS1/BDOHARNESSENDPOINTNAME

The name of the endpoint. Must start with a letter and contain only alphanumeric characters and underscores.

Optional arguments:

iv_targetversion TYPE /AWS1/BDOHARNESSVERSION /AWS1/BDOHARNESSVERSION

The harness version that the endpoint points to and serves invocations from.

iv_description TYPE /AWS1/BDOHARNESSENDPOINTDESC /AWS1/BDOHARNESSENDPOINTDESC

A description of the endpoint.

iv_clienttoken TYPE /AWS1/BDOCLIENTTOKEN /AWS1/BDOCLIENTTOKEN

A unique, case-sensitive identifier to ensure idempotency of the request.

it_tags TYPE /AWS1/CL_BDOTAGSMAP_W=>TT_TAGSMAP TT_TAGSMAP

Tags to apply to the endpoint resource.

RETURNING

oo_output TYPE REF TO /aws1/cl_bdocreateharnendptrsp /AWS1/CL_BDOCREATEHARNENDPTRSP

Examples

Syntax Example

This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.

DATA(lo_result) = lo_client->createharnessendpoint(
  it_tags = VALUE /aws1/cl_bdotagsmap_w=>tt_tagsmap(
    (
      VALUE /aws1/cl_bdotagsmap_w=>ts_tagsmap_maprow(
        key = |string|
        value = new /aws1/cl_bdotagsmap_w( |string| )
      )
    )
  )
  iv_clienttoken = |string|
  iv_description = |string|
  iv_endpointname = |string|
  iv_harnessid = |string|
  iv_targetversion = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lo_harnessendpoint = lo_result->get_endpoint( ).
  IF lo_harnessendpoint IS NOT INITIAL.
    lv_harnessid = lo_harnessendpoint->get_harnessid( ).
    lv_harnessname = lo_harnessendpoint->get_harnessname( ).
    lv_harnessendpointname = lo_harnessendpoint->get_endpointname( ).
    lv_harnessendpointarn = lo_harnessendpoint->get_arn( ).
    lv_harnessendpointstatus = lo_harnessendpoint->get_status( ).
    lv_datetimestamp = lo_harnessendpoint->get_createdat( ).
    lv_datetimestamp = lo_harnessendpoint->get_updatedat( ).
    lv_harnessversion = lo_harnessendpoint->get_liveversion( ).
    lv_harnessversion = lo_harnessendpoint->get_targetversion( ).
    lv_harnessendpointdescript = lo_harnessendpoint->get_description( ).
    lv_string = lo_harnessendpoint->get_failurereason( ).
  ENDIF.
ENDIF.