Skip to content

command_execution_profile

Configuration for Command Execution Profile resource.

(click to see Operations)

Properties

(click to see Operations)

NameData TypePermissionsDescription
append_errors<Boolean>Read-writeAppend Errors.
id<String>Read-writeId is system generated key for all the run command profile..
append_output<Boolean>Read-writeAppend Output.
command_text<String>Read-writeRun Command Text.
Minimum length = 1
Maximum length = 128
profile_name<String>Read-writeProfile name for the run command setting..
Minimum length = 1
Maximum length = 128
tenant_id<String>Read-onlyTenant Id .

Operations

(click to see Properties)

ADD| DELETE| GET (ALL)| GET| UPDATE

Some options that you can use for each operations:

  • Getting warnings in response:NITRO allows you to get warnings in an operation by specifying the "warning" query parameter as "yes". For example, to get warnings while connecting to the NetScaler appliance, the URL is as follows:

    http://<netscaler-ip-address>/nitro/v1/config/login?warning=yes

    If any, the warnings are displayed in the response payload with the HTTP code "209 X-NITRO-WARNING".

  • Authenticated access for individual NITRO operations:NITRO allows you to logon to the NetScaler appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,

    To do this, you must specify the username and password in the request header of the NITRO request as follows:

    X-NITRO-USER:<username>

    X-NITRO-PASS:<password>

    Note: In such cases, make sure that the request header DOES not include the following:

    Cookie:NITRO_AUTH_TOKEN=<tokenvalue>

Note:

Mandatory parameters are marked in red and placeholder content is marked in <green>.

add

URL: https://<MGMT-IP>/nitro/v1/config/command_execution_profile?onerror=<String_value>

HTTP Method: null

Request Payload:

{command_execution_profile: {
<b>"command_text":<String_value></b>,
<b>"profile_name":<String_value></b>,
"id":<String_value>,
"append_errors":<Boolean_value>,
"append_output":<Boolean_value>}}

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "command_execution_profile":[{
"tenant_id":<String_value>,
"append_errors":<Boolean_value>,
"id":<String_value>,
"append_output":<Boolean_value>,
"command_text":<String_value>,
"profile_name":<String_value>}]}

delete

URL: https://<MGMT-IP>/nitro/v1/config/command_execution_profile/id_value<String>

HTTP Method: null

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value> }

get (all)

URL: https://<MGMT-IP>/nitro/v1/config/command_execution_profile

HTTP Method: null

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "command_execution_profile":[{
"tenant_id":<String_value>,
"append_errors":<Boolean_value>,
"id":<String_value>,
"append_output":<Boolean_value>,
"command_text":<String_value>,
"profile_name":<String_value>}]}

get

URL: https://<MGMT-IP>/nitro/v1/config/command_execution_profile/id_value<String>

HTTP Method: null

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "command_execution_profile":[{
"tenant_id":<String_value>,
"append_errors":<Boolean_value>,
"id":<String_value>,
"append_output":<Boolean_value>,
"command_text":<String_value>,
"profile_name":<String_value>}]}

update

URL: https://<MGMT-IP>/nitro/v1/config/command_execution_profile/id_value<String>

HTTP Method: null

Request Payload:

{command_execution_profile:{
<b>"id":<String_value></b>,
"append_errors":<Boolean_value>,
"command_text":<String_value>,
"append_output":<Boolean_value>,
"profile_name":<String_value>}}

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "command_execution_profile":[{
"tenant_id":<String_value>,
"append_errors":<Boolean_value>,
"id":<String_value>,
"append_output":<Boolean_value>,
"command_text":<String_value>,
"profile_name":<String_value>}]}