Deploying Auxiliary Plug-in Servers
When you divide plug-in features between several auxiliary servers, you register each
server with a string identifier that indicates the service it provides. Any plug-in server can
locate a service it needs by using the service identifier to look up the service endpoint URL in
the extension registry record.
When vCenter Server deploys a remote plug-in, it caches the plug-in manifest and configures a routing rule for the reverse HTTP proxy, which directs UI traffic to the manifest server process. If the plug-in includes auxiliary servers, vCenter Server also creates rules to route UI traffic to the auxiliary servers.
VCenter Server maintains a mapping of service
identifiers to proxy URLs. Plug-in code that runs in the browser can access that mapping by
using the
getPluginBackendInfo()
method. The resulting data allows the
JavaScript code to determine the proxy URLs for the services it needs. For more information
about getPluginBackendInfo()
, see vSphere Client JavaScript API:
Application Interface.For more information about registerirg auxiliary
plug-in servers, see Registering Auxiliary Plug-in Servers.