/AWS1/IF_SGM=>CREATEEDGEDEPLOYMENTPLAN()¶
About CreateEdgeDeploymentPlan¶
Creates an edge deployment plan, consisting of multiple stages. Each stage may have a different deployment configuration and devices.
Method Signature¶
METHODS /AWS1/IF_SGM~CREATEEDGEDEPLOYMENTPLAN
IMPORTING
!IV_EDGEDEPLOYMENTPLANNAME TYPE /AWS1/SGMENTITYNAME OPTIONAL
!IT_MODELCONFIGS TYPE /AWS1/CL_SGMEDGEDEPLOYMENTMD00=>TT_EDGEDEPLOYMENTMODELCONFIGS OPTIONAL
!IV_DEVICEFLEETNAME TYPE /AWS1/SGMENTITYNAME OPTIONAL
!IT_STAGES TYPE /AWS1/CL_SGMDEPLOYMENTSTAGE=>TT_DEPLOYMENTSTAGES OPTIONAL
!IT_TAGS TYPE /AWS1/CL_SGMTAG=>TT_TAGLIST OPTIONAL
RETURNING
VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_sgmcreedgedeploymen01
RAISING
/AWS1/CX_SGMRESOURCELIMITEXCD
/AWS1/CX_SGMCLIENTEXC
/AWS1/CX_SGMSERVEREXC
/AWS1/CX_RT_TECHNICAL_GENERIC
/AWS1/CX_RT_SERVICE_GENERIC.
IMPORTING¶
Required arguments:¶
iv_edgedeploymentplanname TYPE /AWS1/SGMENTITYNAME /AWS1/SGMENTITYNAME¶
The name of the edge deployment plan.
it_modelconfigs TYPE /AWS1/CL_SGMEDGEDEPLOYMENTMD00=>TT_EDGEDEPLOYMENTMODELCONFIGS TT_EDGEDEPLOYMENTMODELCONFIGS¶
List of models associated with the edge deployment plan.
iv_devicefleetname TYPE /AWS1/SGMENTITYNAME /AWS1/SGMENTITYNAME¶
The device fleet used for this edge deployment plan.
Optional arguments:¶
it_stages TYPE /AWS1/CL_SGMDEPLOYMENTSTAGE=>TT_DEPLOYMENTSTAGES TT_DEPLOYMENTSTAGES¶
List of stages of the edge deployment plan. The number of stages is limited to 10 per deployment.
it_tags TYPE /AWS1/CL_SGMTAG=>TT_TAGLIST TT_TAGLIST¶
List of tags with which to tag the edge deployment plan.
RETURNING¶
oo_output TYPE REF TO /aws1/cl_sgmcreedgedeploymen01 /AWS1/CL_SGMCREEDGEDEPLOYMEN01¶
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->createedgedeploymentplan(
it_modelconfigs = VALUE /aws1/cl_sgmedgedeploymentmd00=>tt_edgedeploymentmodelconfigs(
(
new /aws1/cl_sgmedgedeploymentmd00(
iv_edgepackagingjobname = |string|
iv_modelhandle = |string|
)
)
)
it_stages = VALUE /aws1/cl_sgmdeploymentstage=>tt_deploymentstages(
(
new /aws1/cl_sgmdeploymentstage(
io_deploymentconfig = new /aws1/cl_sgmedgedeploymentcfg( |string| )
io_deviceselectionconfig = new /aws1/cl_sgmdevselectionconfig(
it_devicenames = VALUE /aws1/cl_sgmdevicenames_w=>tt_devicenames(
( new /aws1/cl_sgmdevicenames_w( |string| ) )
)
iv_devicenamecontains = |string|
iv_devicesubsettype = |string|
iv_percentage = 123
)
iv_stagename = |string|
)
)
)
it_tags = VALUE /aws1/cl_sgmtag=>tt_taglist(
(
new /aws1/cl_sgmtag(
iv_key = |string|
iv_value = |string|
)
)
)
iv_devicefleetname = |string|
iv_edgedeploymentplanname = |string|
).
This is an example of reading all possible response values
lo_result = lo_result.
IF lo_result IS NOT INITIAL.
lv_edgedeploymentplanarn = lo_result->get_edgedeploymentplanarn( ).
ENDIF.