Skip to content

/AWS1/IF_IOX=>SENDMANAGEDTHINGCOMMAND()

About SendManagedThingCommand

Send the command to the device represented by the managed thing.

Method Signature

METHODS /AWS1/IF_IOX~SENDMANAGEDTHINGCOMMAND
  IMPORTING
    !IV_MANAGEDTHINGID TYPE /AWS1/IOXMANAGEDTHINGID OPTIONAL
    !IT_ENDPOINTS TYPE /AWS1/CL_IOXCOMMANDENDPOINT=>TT_COMMANDENDPOINTS OPTIONAL
    !IV_CONNECTORASSOCIATIONID00 TYPE /AWS1/IOXCNCTORASSOCIATIONID OPTIONAL
    !IV_ACCOUNTASSOCIATIONID TYPE /AWS1/IOXACCOUNTASSOCIATIONID OPTIONAL
  RETURNING
    VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_ioxsendmanagedthgcm01
  RAISING
    /AWS1/CX_IOXACCESSDENIEDEX
    /AWS1/CX_IOXINTERNALSERVEREX
    /AWS1/CX_IOXRESOURCENOTFOUNDEX
    /AWS1/CX_IOXSERVICEUNAVAILEX
    /AWS1/CX_IOXTHROTTLINGEX
    /AWS1/CX_IOXUNAUTHORIZEDEX
    /AWS1/CX_IOXVALIDATIONEX
    /AWS1/CX_IOXCLIENTEXC
    /AWS1/CX_IOXSERVEREXC
    /AWS1/CX_RT_TECHNICAL_GENERIC
    /AWS1/CX_RT_SERVICE_GENERIC.

IMPORTING

Required arguments:

iv_managedthingid TYPE /AWS1/IOXMANAGEDTHINGID /AWS1/IOXMANAGEDTHINGID

The id of the device.

it_endpoints TYPE /AWS1/CL_IOXCOMMANDENDPOINT=>TT_COMMANDENDPOINTS TT_COMMANDENDPOINTS

The device endpoint.

Optional arguments:

iv_connectorassociationid00 TYPE /AWS1/IOXCNCTORASSOCIATIONID /AWS1/IOXCNCTORASSOCIATIONID

The ID tracking the current discovery process for one connector association.

iv_accountassociationid TYPE /AWS1/IOXACCOUNTASSOCIATIONID /AWS1/IOXACCOUNTASSOCIATIONID

The identifier of the account association to use when sending a command to a managed thing.

RETURNING

oo_output TYPE REF TO /aws1/cl_ioxsendmanagedthgcm01 /AWS1/CL_IOXSENDMANAGEDTHGCM01

Domain /AWS1/RT_ACCOUNT_ID
Primitive Type NUMC

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->sendmanagedthingcommand(
  it_endpoints = VALUE /aws1/cl_ioxcommandendpoint=>tt_commandendpoints(
    (
      new /aws1/cl_ioxcommandendpoint(
        it_capabilities = VALUE /aws1/cl_ioxcommandcapability=>tt_commandcapabilities(
          (
            new /aws1/cl_ioxcommandcapability(
              it_actions = VALUE /aws1/cl_ioxcapabilityaction=>tt_capabilityactions(
                (
                  new /aws1/cl_ioxcapabilityaction(
                    io_parameters = /AWS1/CL_RT_DOCUMENT=>FROM_JSON_STR( |\{"foo":"this is a JSON object..."\}| )
                    iv_actiontraceid = |string|
                    iv_name = |string|
                    iv_ref = |string|
                  )
                )
              )
              iv_id = |string|
              iv_name = |string|
              iv_version = |string|
            )
          )
        )
        iv_endpointid = |string|
      )
    )
  )
  iv_accountassociationid = |string|
  iv_connectorassociationid00 = |string|
  iv_managedthingid = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lv_traceid = lo_result->get_traceid( ).
ENDIF.