-
-
XenCenter Plug-in Specification Guide
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!
XenCenter Plug-in Specification Guide
This document explains how to write a plug-in for XenCenter, the GUI for Citrix Hypervisor. Using the plug-in mechanism third-parties can:
-
Create menu entries in the XenCenter menus linked to an executable file or PowerShell script, including full use of the Citrix Hypervisor PowerShell Module (XenServerPSModule) cmdlets.
-
Cause a URL to be loaded into a tab in XenCenter.
The XenCenter plug-in mechanism is context aware, allowing you to use XenSearch to specify complicated queries. Also, plug-ins can take advantage of contextual information passed as arguments to executables or as replaceable parameters in URLs.
A XenCenter plug-in consists of the following components:
-
An XML configuration file.
-
A resource DLL for each supported locale. Currently XenCenter exists in English and Japanese versions only.
-
The application and any resources it requires.
Put these components of a plug-in in a subdirectory of the XenCenter installation
directory. For example, a default installation of XenCenter requires that a plug-in
reside in C:\Program Files (x86)\Citrix\XenCenter\Plugins\<organization_name>\<plug-in_name>
XenCenter loads all valid plug-ins found in subdirectories of the plug-ins directory when it starts:
-
The plug-in name (<plug-in_name>) must be the same as the directory in which it is placed.
-
The resource DLL and the XML configuration file must follow these naming conventions:
<plug-in_name>.resources.dll<plug-in_name>.xcplugin.xml
For example, if your organization is called Citrix and you write a plug-in called
Example which runs a batch file called do_something.bat, the following files must exist:
C:\Program Files (x86)\Citrix\XenCenter\Plugins\Citrix\Example\Example.resources.dllC:\Program Files (x86)\Citrix\XenCenter\Plugins\Citrix\Example\example.xcplugin.xmlC:\Program Files (x86)\Citrix\XenCenter\Plugins\Citrix\Example\do_something.bat
These paths assume that you use the default XenCenter installation directory.
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.