-
-
-
-
Importing and synchronizing StyleBooks from GitHub repository
-
Simplified migration of Citrix ADC application configuration using StyleBooks
-
-
Use ADM log messages for managing and monitoring your infrastructure
-
-
Citrix ADC automation using Citrix ADM in Cisco ACI hybrid mode
-
Citrix ADC device package in Cisco ACI's cloud orchestrator mode
-
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!
Import and export configuration templates
You can export the configuration templates from any Citrix Application Delivery Management (ADM). You can also import the file to the same or another Citrix ADM at any time in future. The configuration templates data (like configuration commands, variable definitions, and parameters) are not lost.
You can export the configuration templates to a .json file format and save it in the local folder. You can import configuration template .json files into Citrix ADM. This file might be new or the one that you have exported from the same or other Citrix ADM.
To export the configuration templates:
-
Navigate to Networks > Configuration Jobs > Configuration Templates.
-
Click the Add button to create the configuration template.
-
On the Create Configuration Template page, specify the configuration template name, and choose the instance type. Under Configuration Editor, select configuration source as Configuration Template from the drop-down menu. You can drag the existing configuration templates to the configuration editor. Click Create.
-
Navigate to Networks > Configuration Jobs > Configuration Templates to view the templates created in the list of Configuration Templates.
-
Select the newly created configuration template and click the Export button.
The corresponding configuration template gets downloaded on your local system in .json format.
To import the configuration templates:
-
Navigate to Networks > Configuration Jobs > Configuration Templates and click the Import button. Select the path where you have the .json files of the configuration template and upload the .json files. It is highly recommended to upload the .json files that you have exported already.
-
You can also import the configuration template using File option on Configuration Editor.
-
Select File from the drop-down menu in the Configuration Editor.
-
Select Choose File (.json files) from your local system and upload the configuration template .json files.
Note
-
Every new imported template is stored with a new id string.
-
You can import the configuration templates only if the file is saved in the .json format. If you import the configuration templates other than .json files, from your local system, it shows an error and fails the import of the files.
-
Share
Share
In this article
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group 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 Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.