Remote Plug-in Deployment
Last Updated December 16, 2024

When the vSphere Client discovers a remote plug-in, it schedules the plugin for deployment. vCenter Server takes the following steps to deploy a remote plug-in in the vSphere Client:
  • Download the remote plug-in manifest,
    plugin.json
    , from the location specified in the
    ClientInfo
    property registered in the ExtensionManager. When you use the extension-registration script provided in the SDK this is the value of the
    -pu
    or
    -pluginUrl
    argument. vCenter Server downloads your plug-in manifest into
    /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/
    your_plugin_name
    -
    your_plugin_version
    .
  • Parse the plug-in manifest to determine whether its specified version and environment are compatible with deployment on this vCenter Server instance.
  • Parse the plug-in manifest to determine what views will be shown in the user interface, and add them to an internal extension point table.
  • Configure the vCenter Server reverse HTTP proxy to route plug-in UI traffic to the remote plug-in server or servers.
After these steps complete successfully, the vSphere Client user interface displays a notification that the remote plug-in is installed.