To improve the performance of your plug-in package, the initial download and deployment time after the first time the user logs into the vSphere Client, must be less than a minute.

To ease the testing and debugging of your plug-in package, you must include the build number in the dot-separated version number of the plug-in package when you register the plug-in as a vSphere Client extension.

To prevent deployment issues when you try to deploy a new version of a registered plug-in package, make sure that you modify the version property of your plug-in package in the plugin-package.xml manifest file.

To prevent deployment issues when you try to deploy a plug-in package with the same version, make sure that you unregister the plug-in package by removing the plug-in as a vCenter Server extension. You must also manually delete the cached files of the plug-in package that are stored on the Virgo server in one of the following locations:

To avoid performance issues, make sure that your plug-in package has only one version registered with the vCenter Server. You must not change the value of the key property of the vCenter Server Extension data object between releases.

To verify easily the deployment of your plug-in package and monitor for any issues related to your plug-in, you must know how to work with the Virgo server log files. You can find these log files in one of the following locations:

The vsphere_client_virgo.log file contains the log information that the Virgo server generates. Problems usually start with the [ERROR] tag. Use your plug-in package name or the bundle symbolic name to detect errors caused by your plug-in.

To log information about your plug-in package, you must use the default logging mechanisms of the vSphere Client. Use the Apache Log4j logging framework to provide debugging information for your plug-in package. The Virgo server uses the Simple Logging Facade for Java (SLF4J) logging API.