-
-
-
trigger_detail
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
trigger_detail
Configuration for Trigger Detail resource.
Properties
(click to see Operations )
Name | Data Type | Permissions | Description |
---|---|---|---|
expiry | <String> | Read-write | Time at which the trigger should end.Format:YY:MM:DD:HH:MM.Applicable for trigger of type fixed. |
parent_name | <String> | Read-write | . |
daily_time | <String> | Read-write | Time of the day.Format is HH:MM where HH is hours and MM is minutes.Applicable for trigger of type daily. |
trigger_type | <String> | Read-write | Trigger type.Possible values: fixed,daily,weekly,monthly.
Minimum length = 1 Maximum length = 128 |
recur_hr | <String> | Read-write | Recur interval in hours. Applicable for trigger of type fixed. |
duration | <String> | Read-write | Duration in days for which the trigger should last. Applicable for trigger of type fixed. |
description | <String> | Read-write | Trigger description. |
parent_id | <String> | Read-write | . |
monthday_time | <String> | Read-write | Days of the month.Format is DD:HH:MM where DD is either 1-31 or last for days of the month,HH is hours and MM is minutes.Applicable for trigger of type monthly.. |
id | <String> | Read-write | . |
weekday_time | <String> | Read-write | Days of the week.Format is Day:HH:MM where Day is 0-6 for sunday-saturday,HH is hours and MM is minutes.Applicable for trigger of type weekly. |
recur_min | <String> | Read-write | Recur interval in minutes. Applicable for trigger of type fixed. |
start | <String> | Read-write | Time at which the trigger should start.Format:YY:MM:DD:HH:MM. |
Operations
(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:
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
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
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.