Configuration for Filter Schedule Details resource.
(click to see Operations )
|scheduleEndTimesEpoch||<String>||Read-write||Schedule time epoch (string representation of 11 digit numbers)..|
|scheduleStartTimesEpoch||<String>||Read-write||Schedule time epoch (string representation of 11 digit numbers)..|
|parent_name||<String>||Read-write||Name of the parent resource.|
|endRecurrenceTimes||<String>||Read-write||Comma separated recurrence epoch times at which job is to be executed.|
|id||<String>||Read-write||Id is system generated key for all the events.|
|startRecurrenceTimes||<String>||Read-write||Comma separated recurrence epoch times at which job is to be executed.|
|parent_id||<String>||Read-write||Id of the parent resource.|
(click to see Properties )
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:
Note: In such cases, make sure that the request header DOES not include the following:
Note: Mandatory parameters are marked in red and placeholder content is marked in green
The following parameters can be used in the nitro request : onerror <String_value>
Use this parameter to set the onerror status for nitro request. Applicable only for bulk requests.
Default value: EXIT
Possible values = EXIT, CONTINUE