Deployment Requirements for a Remote Plug-in for the vSphere Client

To prepare a remote plug-in for deployment, you must prepare several files and launch some processes.

Deployment of a remote plug-in takes place at run time, but you must make preparations in advance. You need to do the following to prepare for plug-in deployment:

Run a web server that provides plug-in components on demand.
Run your plug-in server binary. The plug-in server runs on a virtual or physical machine of your choice, but it must be on the same machine as the web server.
Prepare a plug-in manifest file, plugin.json, that specifies the plug-in components. The manifest file must be on the same machine as the web server.
Register your plug-in with a vCenter Server instance. To register, you need the URL and credentials to access vCenter Server. You also need the certificate thumbprint of your plug-in server and the URL of your plug-in manifest file. The script arguments are shown in the following example.
```
./extension-registration.sh	-action registerPlugin -remote \
  -url https://myvcenter/sdk \
  -username	[email protected] -password mysecret \
  -key com.mycompany.myplugin -version 1.0.0 \
  -pluginUrl https://mydevbox:8443/myplugin/plugin.json \
  -serverThumbprint 19:FD:2B:0E:62:5E:0E:10:FF:24:34:7A:81:F1:D5:33:19:A7:22:A0 \
  -c 'Example, Inc.' -n 'Remote Plug-in' -s 'This is a remote plug-in'
```
For more information about the plug-in registration script, see vSphere Client Plug-in Registration Tool