Advanced Considerations for Remote Plug-in Servers

A remote plug-in for the vSphere Client has both a server portion and a user interface portion. You can use any coding language or framework you choose for the server portion. Your plug-in server must generally provide the following functionality:

• A web application server that serves both the plug-in manifest file and the plug-in user interface files.
• A fixed Service Provider Interface that responds to vSphere Client requests for dynamic view content, such as menus.
• Data access and computation services on behalf of the plug-in user interface views, if needed.
• Session cloning service to authenticate with the vCenter Server Web Services API, if needed.