The remote plug-in does not display in
the vSphere Client user interface.
Problem
The plug-in does not appear in the
object navigator, but it is listed in the vSphere Client under .Cause
The plug-in was not registered correctly as a remote plug-in, which causes the
vSphere
Client
to assume that it is a local plug-in. When the
vSphere
Client
tries to download the plug-in manifest, it expects a .zip file but finds a
.json file instead.
You can verify the cause of the problem by
searching the vsphere-client-virgo.log file for an error message saying that
the
vSphere
Client
did not find a ZIP file at the plug-in manifest location:
Couldn't
open plugin zip file when trying to verify the signature of plugin
extension.key:extension.version java.util.zip.ZipException: error in opening zip
file.
Solution
-
On the machine that runs the plug-in server, change to the directory that contains the plug-in manifest.
For example: cd samples/remote-plugin-sample/target/classes/static
-
Unregister the plug-in.
For example: $tools/extension-registration.sh -action unregisterPlugin -k sample.plugin -url https://vc-svr.example.com/sdk -u [email protected] -p secret
-
Reregister the plug-in, specifying that it is
a remote plug-in.
For example, you can use the plug-in
registration tool in the SDK: $tools/extension-registration.sh -action
registerPlugin -remote -k sample.plugin -v 1.0.0 -url https://vc-svr.example.com/sdk
-u [email protected] -p $secret -pluginUrl $pluginurl -serverThumbprint
$thumbprint -c 'Example Inc.' -n 'Example Plug-in' -s 'This plug-in is registered with
the remote keyword.'