I am not understanding the full relationships and how the system works when I install a plugin when there are multiple vCenter servers present and I am wondering if I am doing the plugin registration correctly.
We have a setup with one SSO server and multiple vCenter servers. When our plugin is installed, it is installed against one of the vCenter servers. But I see the plugin appear even if I access the webclient through one of the other vCenter server addresses. In addition if I can go install our plugin against more than one vCenter server, which means that at least our backend server side ends up on those servers.
So first I have a best practices question, in an environment such as this, should the plugin only be installed against one of the vCenter servers, especially since we have a backend component?
For registering our plugin, we are using the Extension manager (as we were before with the traditional C# client). In this multiple vCenter server environment, should I then contact all of the vCenter servers individually and use the extension manager to register out plugin on them as part of my installation process?
Do all of the vCenter servers had a running webclient (i.e. virgo) process running and serving up the webclient?
Is there a document or FAQ or forum entry that gives information about how to work within this multiple vcenter server/sso/webclient environment in terms of issues such as this?
↧
Webclient, vCenter Server, SSO and their relationships for plugin installation
↧
